chore: bump pom to 0.3.1-SNAPSHOT after v0.3.1 release#11
Closed
aksOps wants to merge 1 commit into
Closed
Conversation
v0.3.1 was tagged from main carrying the LTA 2026.1 manifest refresh and the Nexus-bootstrap CLI wrapper. publish.yml's versions:set step runs at release time so the source pom did not strictly need to track the released version, but advancing the in-development version keeps the pom honest about what's on main going forward.
|
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.
Summary
Post-release pom bump. v0.3.1 was tagged from
main(commit400cf9d)carrying the LTA 2026.1 manifest refresh and the Nexus-bootstrap CLI
wrapper from #10. This advances the in-development version so the pom
on
mainreflects what's actually being worked on next.publish.ymlrunsversions:setat release time (the tag drives thereleased version), so the source pom didn't strictly need to track the
released version — but leaving
0.3.0-SNAPSHOTonmainafterv0.3.0shipped was the source of recent confusion (the BoM in
manifest.jsonwas also stale against the pom's LTA pins). Keeping the in-development
pom version honest is the small bit of hygiene that avoids the next
version-skew bug.
Test plan
pom.xml. No code or test changes.