-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update coppercore to 2025 #62
Conversation
@jkleiber What would you prefer that I version this code as? The ideas I have in mind are 2025.0.0-beta, or 2024.12.5-beta, although I find the 2024 to be slightly misleading since it's now using 2025 code. |
I prefer 2025.0.0-beta since it is clearly 2025 and a prerelease |
@aidnem after you merge this, create a release on github to automatically add the new version to maven central We can always release to the same version twice if we want (this is not great practice but we're still early enough into development that it's fine imo) |
@jkleiber would you mind taking a look at the draft release to make sure everything is okay? I've never made a release before. |
@aidnem LGTM |
Thanks, release published now. |
@jkleiber should the action automatically run to publish or do I have to run it myself? |
@aidnem it should run automatically but it looks like it didn't. I might have broken the workflow when I was fixing maven publishing in general. For this one try running it manually |
Okay, I ran it and it looks like it's published now. I'll try importing and using it tomorrow. |
Changes: