chore(renovate): never bump io.plugwerk SDK pins — examples must track latest SNAPSHOT#45
Merged
Merged
Conversation
…k latest SNAPSHOT Both gradle/libs.versions.toml pin plugwerk = "1.0.0-SNAPSHOT" by design so day-to-day development tests against the latest Plugwerk server build and surfaces upstream regressions early (e.g. SPI breaking changes land in the SNAPSHOT first, examples catch them before downstream users do). Renovate just opened #44 to bump to v1.0.0 (the freshly released stable), which would freeze the test target. Add an ignore rule for io.plugwerk:** on the maven datasource so future SDK releases don't generate the same PR again. Manual bump to a fixed release stays an explicit step at examples- repo release time.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Both
gradle/libs.versions.tomlfiles pinplugwerk = "1.0.0-SNAPSHOT"by design. The whole point of the examples repo during normal development is to verify that the apps still build and run against the latest Plugwerk server / SDK build — pinning to a fixed release would freeze the test target and defeat that.Renovate just opened #44 to bump both pins to v1.0.0 (the stable that landed today), and without an ignore rule it will keep doing this for every future Plugwerk release.
What
Adds a
packageRulesentry that disables Renovate updates for anyio.plugwerk:**artifact resolved via the maven datasource. Thedescriptionfield is included so it lands in any future Renovate dashboard / PR body that mentions the rule.After merge: close #44 manually (Renovate will not reopen it once the rule is in place).
Out of scope
Bumping the pin to a concrete release version (
1.0.0,1.0.1, …) remains an explicit step taken when an examples-repo release of the same name is cut. That stays a manual edit, not a Renovate-driven one.