Skip to content

docs: catalog updates via the spec-kit extension submission issue (maintainer guidance)#60

Merged
ashbrener merged 1 commit into
mainfrom
011-catalog-process
Jun 10, 2026
Merged

docs: catalog updates via the spec-kit extension submission issue (maintainer guidance)#60
ashbrener merged 1 commit into
mainfrom
011-catalog-process

Conversation

@ashbrener

@ashbrener ashbrener commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Remediates the only feedback on the now-merged catalog PR github/spec-kit#2893:

@mnriem: "Thank you! Note going forward please use an extension submission issue"

The launch gate is cleared — the community catalog now lists linear at v0.3.0 with spec-kit-linear-sync URLs. This PR codifies the process so future bumps (e.g. v0.4.0 with spec 007) go via the upstream Extension submission issue template instead of a direct catalog PR.

Docs-only; markdownlint clean.

Remediates the maintainer's guidance on PR #2893 (merged 2026-06-09): catalog
updates should be requested via the github/spec-kit 'Extension submission' issue
template, not a direct PR. Adds a 'Releasing & updating the community catalog'
section to CONTRIBUTING so the next release (e.g. v0.4.0 with spec 007) follows
the process. Direct catalog PRs are deprecated for this repo; id stays 'linear'.
@ashbrener ashbrener merged commit 3669507 into main Jun 10, 2026
6 checks passed
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