-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Prepare next release #1325
Comments
Yes indeed, I already bumped the "base version" in the Line 5 in 9cfdb17
https://typelevel.org/sbt-typelevel/faq.html#what-is-a-base-version-anyway |
I think before the next release, the You can generate a new key here: If you use the online key generator, make sure to delete the |
Thanks, I will regenerate one. |
@armanbilge scala-native release would be highly appreciated as well. |
@yuriy-yarosh indeed, fortunately there is a snapshot available while we are waiting :) |
Sorry for the delay. I will try to do it next week. |
@armanbilge I updated PGP_SECRET and deleted PGP_PASSPHRASE. What is the next step? should I create and publish a tag? |
@julien-truffaut great! Yes, you can either create/push a tag locally, or you can just create the release from the GH UI. |
Thanks, I didn't know about this UI. I triggered the build, let's cross our fingers :) |
publication failed with this error:
|
@julien-truffaut did you submit the public key to the key server as explained here? |
Yes but I must have made a mistake. I regenerated a key and restarted the build and now it works :) Thanks |
Artifacts are live: |
I will try to write the release notes over the next week or two. |
There's also an "auto-generate release notes" button in the GH UI :) |
Yeah but it isn't great |
@armanbilge I updated the release notes. If you have a minute wold you mind reviewing it? |
@julien-truffaut LGTM 👍 thanks! |
Here is the list of changes since 3.1.0: v3.1.0...master
We bumped the major version of the scala compiler to 3.2.1. I am not sure what is the impact.
I think the next version will be 3.2.0.
The text was updated successfully, but these errors were encountered: