-
Notifications
You must be signed in to change notification settings - Fork 92
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
Publish next release (to publish Scala 3 Native support) #596
Comments
@SethTisue maybe move forward with it? This is a blocker for scalatest/scalatest#2097 which is blocking scalatests for scala-native for scala 3+ |
a 2.0.2 release job failed with:
|
Volunteer to suggest what the appropriate solution is here and PR a fix...? I cannot spare the time this week or next. |
The lazy option would be to just bump to 2.1.0 😬 |
@nightscape an another way is switch Thus, @SethTisue any chance to release it as |
I'm happy to go along with whatever the consensus here appears to be. At the moment, #598 is failing CI, so that needs to be fixed first. (I'm trying to minimize my involvement here to pushing whatever release tag y'all tell me to push — if another maintainer isn't available to push one theirselves, which would be my first choice. Any of y'all interested in joining the volunteer maintainer crew here?) |
@SethTisue to fix my branch you (or someone else) must to remove tag v2.0.2 from GitHub. as soon as you did it, my PR should work |
That I can do :-) I deleted the tag and closed/reopened the PR which made the actions re-run, but isn't re-running the CircleCI jobs. I don't know anything about CircleCI (and since @ashawley has been a lot less active lately, maybe we should just remove that stuff, since he was the one managing it); perhaps you'll need to push a commit with a different hash in order to make that part re-run. |
@SethTisue base on that is failed in #598 I believe that now you must release As soon as (Checks and versioning and release process of |
https://github.com/scala/scala-xml/releases/tag/v2.1.0, publish job at https://github.com/scala/scala-xml/actions/runs/2088914876
Release process seems clean to me, courtesy of sbt-ci-release; a maintainer (currently @ashawley or I) just pushes a tag, done. But if you have specific suggestions, perhaps they'd be accepted. As for the checks and versioning aspect, that's coming directly from https://github.com/scalacenter/sbt-version-policy, unless you see some repo-specific aspect here in this repo that could be improved. If it's about sbt-version-policy, you might consider lodging that feedback as one or more tickets there. (cc @julienrf) |
@SethTisue I see. I mean that mix Anyway, now it should be much better. |
https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_native0.4_3/2.1.0/ 🎉 thanks all who participated |
note that #592 made some build changes that haven't been tested yet in a releasing context, so this release should be done with some extra care
have any other changes been made since the last release? what should the new version number be?
The text was updated successfully, but these errors were encountered: