chore(catalog): add publish-catalog.sh — file catalog bumps via the issue template - #87
Open
ashbrener wants to merge 1 commit into
Open
chore(catalog): add publish-catalog.sh — file catalog bumps via the issue template#87ashbrener wants to merge 1 commit into
ashbrener wants to merge 1 commit into
Conversation
…ssue template spec-kit now intakes community-catalog adds/bumps through a GitHub issue (Extension Submission template), NOT a hand-edited PR to extensions/catalog.community.json — direct-JSON PRs are closed-with-redirect (github/spec-kit#3133). Our v0.8.0 catalog PR (github/spec-kit#3201) was on that deprecated path and sat unmerged for ~6 weeks; it has been closed and re-filed as github/spec-kit#4100 via the template. Port the sibling's scripts/publish-catalog.sh (spec-kit-jira-sync #25) so the correct path is one command after `gh release create`: scripts/publish-catalog.sh v0.8.0 It pre-fills the submission from extension.yml + the released tag (id, name, version, description, author, repo, download URL, license, homepage, docs, changelog, speckit floor, command count), pre-flights that the tag's archive returns HTTP 200, and uses the local `gh` login — no fork, no PAT, no JSON edit. Only the four sibling-specific values differ (CATALOG_ID, CATALOG_NAME, EXT_REPO, TAGS). Release-tooling only; no runtime, command, or behaviour change.
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
spec-kit changed how it intakes community-catalog adds/bumps: submissions now go through a GitHub issue (Extension Submission template), not a hand-edited PR to
extensions/catalog.community.json. Direct-JSON PRs are closed-with-redirect — see github/spec-kit#3133.Our v0.8.0 catalog PR (github/spec-kit#3201) was on that deprecated path. It sat unmerged for ~6 weeks and had
CHANGES_REQUESTED; the maintainer's note was "going forward please use extension submission issue template." It's now closed and re-filed correctly as github/spec-kit#4100.The sibling
spec-kit-jira-syncalready solved this (its #25). This ports that tooling so we don't repeat the mistake next release.What
scripts/publish-catalog.sh— one command aftergh release create:It pre-fills the submission issue from
extension.yml+ the released tag (id, display name, version, description, author, repository, download URL, license, homepage, documentation, changelog, spec-kit floor, command count), pre-flights that the tag's archive returns HTTP 200 so a broken install link fails before the issue is opened, and uses your localghlogin — no fork, no PAT, no JSON edit.Only four values differ from the sibling copy (
CATALOG_ID,CATALOG_NAME,EXT_REPO,TAGS), all env-overridable; the script documents the copy-to-a-sibling checklist inline.Verification
shellcheck --shell=bash --severity=styleclean.