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

feat: add Scala release workflow #79

Merged
merged 3 commits into from
Mar 13, 2024
Merged

Conversation

tjsilver
Copy link
Contributor

What does this change?

Adds the Scala release workflow to allow for releasing to Sonatype via running a GH action.

How to test

Post-merge, run the release workflow as per the instructions.

How can we measure success?

This really improves the release process for this library, and should make it a lot easier to make a release.

@tjsilver tjsilver requested a review from rtyley March 12, 2024 16:45
Copy link
Member

@rtyley rtyley left a comment

Choose a reason for hiding this comment

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

I added one extra fix with 1693e72 but this looks awesome!

You could also add a Scaladex badge to the ReadMe - and remove the reference to BinTray in there!

commitNextVersion,
pushChanges
)
scalacOptions := Seq("-release:11")
Copy link
Member

Choose a reason for hiding this comment

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

I like this, but do be aware that this will force any project using this library to upgrade to Java 11 (not a bad thing!).

We should be on Java 11 everywhere, but simple-configuration is used in a lot of places and it's possible some of them are still on Java 8! They really should upgrade...

@tjsilver tjsilver merged commit 9886fe9 into main Mar 13, 2024
1 check passed
@tjsilver tjsilver deleted the ts/add-scala-release-workflow branch March 13, 2024 10:32
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.

2 participants