Repository navigation
feat(dx): release hooks and the extension registry docs (#1487, part 5b) - #1624
Merged
Merged
Conversation
…tension registry docs (#1487, part 5b) After a Release, repository_dispatch querya-release goes to the registry (test the new version, refresh compat.json) and to the template (move its image tag and CI matrix). docs/extension-registry.md documents the whole path from the template to the Marketplace; the checklist, README, changelog and dev-container guide point to it.
github-actions
Bot
added
bug
Closed
5 tasks
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.
Part of #1487, step 5, plus the documentation of the whole extension-author path.
release-hooks.yml: after a Release succeeds,repository_dispatchquerya-releasewith the version toQueryaHub/extensions(tests every record against it, refreshescompat.json) andQueryaHub/extension-template(branch + PR, or an issue, moving its image tag and CI matrix). Needs the secretQUERYA_DISPATCH_TOKEN; without it the job only warns. Thequerya-testdb-*andquerya-headlessimages already have their own workflows on the same Release; the Feature does not follow releases.docs/extension-registry.md: the path from the template to the Marketplace, what the app trusts and hides, the index format, how the registry follows releases, the one-time token setup, the nightly check and its issues. Linked fromdocs/README.md,extension-testing.md,dev-containers.md(its Known gaps are updated), the release checklist and the CHANGELOG.The registry side (dispatch handling, issues per failing record) and the template side (
querya-release.yml) are already pushed in their own repositories. Template dry run with 0.4.19 passed (no changes needed); the version-rewrite step was checked locally. The dispatch itself is untested until the secret exists.