Skip to content

docs(skill): update release-pipeline for the eras model - #25

Draft
amondnet wants to merge 1 commit into
mainfrom
docs/skill-eras-update
Draft

docs(skill): update release-pipeline for the eras model#25
amondnet wants to merge 1 commit into
mainfrom
docs/skill-eras-update

Conversation

@amondnet

@amondnet amondnet commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Brings .claude/skills/release-pipeline/SKILL.md back in line with scripts/lib/upstream-sources.ts
after #15, #21 and #24.

  • Support section now describes eras instead of a single minimumVersion: a table of the two
    Spring Boot eras (3.3.0<4.0.0 synthesized, >= 4.0.8 archive) with the component path and
    where 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).
  • Detection section describes the actual gate — era membership, then requiredArtifactUrls +
    unpublishedArtifacts bounded at PROBE_CONCURRENCY, run by both detect-upstream-versions.ts
    and fetch-upstream.ts.
  • "Going below the floor" became "A version outside every era", carrying ADR-0004's measurement
    (3.5.16's bare checkout: 350 unresolved attributes, 837 unresolved configprop:, 326 empty
    include-code::) as the bar a new era has to clear.
  • New-project checklist moves componentPath / archiveClassifiers into eras.
  • Notes the 3.x generated-appendix gap, the new scripts/lib/ modules, and two operational facts
    found while publishing boot-4.0.8 / boot-4.1.1: catalog pull requests conflict when two
    releases are open at once, and they get no ci.yml run because GITHUB_TOKEN-created pull
    requests 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.ts that replaced the per-project minimumVersion, and records two release-operations facts learned while publishing boot-4.0.8 / boot-4.1.1. Documentation only; no pipeline behavior changes.

Doc updates

  • Support table now describes two eras — 3.3.0<4.0.0 synthesized from the tag plus metadata jars, >= 4.0.8 from 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).
  • Detection section now describes the actual gate: era membership, then requiredArtifactUrls HEAD-probed via unpublishedArtifacts at PROBE_CONCURRENCY, shared by detect-upstream-versions.ts and fetch-upstream.ts.
  • "Going below the floor" becomes "A version outside every era," with ADR-0004's measurement (3.5.16: 350 unresolved attributes, 837 unresolved configprop:, 326 empty include-code::) as the bar new eras must clear.
  • New-project checklist moves componentPath and archive classifiers into eras; notes the 3.x generated-appendix gap and the new scripts/lib/ modules.
  • Records that catalog pull requests conflict when two releases are open at once and get no ci.yml run because GITHUB_TOKEN-created pull requests do not trigger workflows.

Written for commit 2b64261. Summary will update on new commits.

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.
@sonarqubecloud

Copy link
Copy Markdown

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@codecov

codecov Bot commented Sep 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant