docs(skill): update release-pipeline for the eras model - #25
Draft
amondnet wants to merge 1 commit into
Draft
Conversation
PR #15 replaced the per-project `minimumVersion` with a sequence of layout eras, so the skill's support table, new-project checklist and below-the-floor section described a shape the code no longer has. Also records why batched releases conflict on catalog.json.
|
Up to standards ✅🟢 Issues
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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
Brings
.claude/skills/release-pipeline/SKILL.mdback in line withscripts/lib/upstream-sources.tsafter #15, #21 and #24.
erasinstead of a singleminimumVersion: a table of the twoSpring Boot eras (
3.3.0–<4.0.0synthesized,>= 4.0.8archive) with the component path andwhere each era's generated half comes from, plus why the eras are not contiguous (3.2 predates the
component, 4.0.0–4.0.7 fall between them, 4.1.0 is an unpublished-artifact fact probed over the
network rather than an era boundary).
requiredArtifactUrls+unpublishedArtifactsbounded atPROBE_CONCURRENCY, run by bothdetect-upstream-versions.tsand
fetch-upstream.ts.(3.5.16's bare checkout: 350 unresolved attributes, 837 unresolved
configprop:, 326 emptyinclude-code::) as the bar a new era has to clear.componentPath/archiveClassifiersintoeras.scripts/lib/modules, and two operational factsfound while publishing
boot-4.0.8/boot-4.1.1: catalog pull requests conflict when tworeleases are open at once, and they get no
ci.ymlrun becauseGITHUB_TOKEN-created pullrequests do not trigger workflows.
Documentation only; no pipeline behavior changes.
Summary by cubic
Updates the release-pipeline skill doc to match the layout-era model in
scripts/lib/upstream-sources.tsthat replaced the per-projectminimumVersion, and records two release-operations facts learned while publishingboot-4.0.8/boot-4.1.1. Documentation only; no pipeline behavior changes.Doc updates
3.3.0–<4.0.0synthesized from the tag plus metadata jars,>= 4.0.8from the Maven Central content archive — and explains why they are not contiguous (3.2 predates the component, 4.0.0–4.0.7 have no archive, 4.1.0 is a publication fact probed over the network).requiredArtifactUrlsHEAD-probed viaunpublishedArtifactsatPROBE_CONCURRENCY, shared bydetect-upstream-versions.tsandfetch-upstream.ts.configprop:, 326 emptyinclude-code::) as the bar new eras must clear.componentPathand archive classifiers intoeras; notes the 3.x generated-appendix gap and the newscripts/lib/modules.ci.ymlrun becauseGITHUB_TOKEN-created pull requests do not trigger workflows.Written for commit 2b64261. Summary will update on new commits.