Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fix] Simplify release mechanism by removing scapegoat selection #1051

Merged
merged 1 commit into from
Jul 12, 2021

Conversation

dzajkowski
Copy link
Contributor

When bumping sbt a scapegoat selection mechanism was removed. It's still required.

@dzajkowski dzajkowski force-pushed the fix/revert-scapegoat-plugin-version branch from 4990ab1 to 2379374 Compare July 12, 2021 07:49
@dzajkowski dzajkowski changed the title [Fix] Revert scapegoat selection mechanism [Fix] Simplify release mechanism by removing scapegoat selection Jul 12, 2021
@dzajkowski dzajkowski merged commit 67db780 into develop Jul 12, 2021
@dzajkowski dzajkowski deleted the fix/revert-scapegoat-plugin-version branch July 12, 2021 08:23
@@ -48,14 +48,13 @@ export CI_SONATYPE_RELEASE=$"; bytes/sonatypeBundleRelease; rlp/sonatypeBundleRe
# so as a workaround the combos are called here explicitly.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you leave that comment for historic reason for why release was introduced in the first place?

By the way it's possible now that ci-release could handle everything.

As per my other comment here, inserting a + before each module would do the cross release, and then there wouldn't be a need to repeat the exact scala versions here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants