fix(catalog): regenerate the root README after the http-action 0.1.1 bump - #50
Merged
Conversation
…bump The 0.1.1 release updated http-action's manifest, changelog, and the plugins.json entry, but the catalog table in the root README was left at 0.1.0. The `catalog:check` CI step compares the generated catalog against what is committed, so main has been red since the release merged. Regenerated with `npm run catalog`; README.md is the only file that drifted.
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
mainhas been failing CI since the http-action 0.1.1 release merged. The failing step isCatalog up to date (plugins.json, READMEs, version↔changelog), which runsnode scripts/catalog.mjs --check.The 0.1.1 release updated
http-action/manifest.json,http-action/CHANGELOG.md,http-action/README.md, and theplugins.jsonentry, but the catalog table in the rootREADME.mdwas left at0.1.0. Sincecatalog.mjsregenerates that table from the manifests and CI compares its output against what is committed, the stale version cell fails the check.Change
Regenerated the catalog with
npm run catalog.README.mdis the only file that drifted —plugins.jsonwas already correct at0.1.1.Verification
Confirmed the failure reproduces on the release merge commit in a clean checkout, and that the regenerated output matches this change exactly.
Local run of the CI steps on this branch:
npm run typecheck— passesnpm test— 435 passing, 0 failingnpm run catalog:check—Catalog up to date (10 plugin(s)).Note
CI was already red on the release PR before it merged. Requiring the
cicheck to pass in branch protection would keep this class of drift from reachingmain.