-
Notifications
You must be signed in to change notification settings - Fork 450
-
Notifications
You must be signed in to change notification settings - Fork 450
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
Release policy #2235
Comments
And we can publish snapshots on main branch, users can try out them as a workaround. I did this on |
Excellent point @Goooler. We have JitPack setup, you can grab any commit you want at any time, see these instructions. |
We should get rid of using jitpack. We are using spotless/gradle/java-publish.gradle Lines 19 to 29 in 4552da0
|
There are few thing to do:
Some work has been addressed in #2236. |
I don't like I love JitPack, because it's only a tiny bit harder to grab HEAD, but I know exactly which commit I'm getting, and I can even commit it and know that my old commits will be buildable / repeatable in the future. Swapping |
You can always pin snapshots on a specific version like pluginManagement {
repositories {
maven("https://oss.sonatype.org/content/repositories/snapshots/")
}
}
plugins {
id("com.gradleup.shadow") version "8.3.0-20240808.050945-5" // a snapshot of 8.3.0
} |
Figuring out which code is generating that snapshot is ambiguous. If it can be added without throwing out our current release pipeline, I'm okay with it, but I still think JitPack is a strictly better option for this usecase. |
Please note that this does not work with how gradle plugins are resolved without extra steps! Remember that when you depend on a plugin by id, it actually resolves the module |
No need to add an extra resolution strategy if you have published plugin markers. This is why I want to migrate to vanniktech in #2236, it will publish both plugin coordinates and markers. |
I wasn't talking about resolution strategies. If both plugin markers and the actual plugin are published with |
The whole point of Spotless is that formatting should not matter. If your formatting plugin is creating "new release" notifications every week then formatting is taking up more time in the ecosystem than it should.
Please don't spam other issues with comments related to "release please!". Keep that here.
The text was updated successfully, but these errors were encountered: