Repository navigation
Publish specification 0.3.0 and keep spec and contract pins current - #116
Merged
Merged
Conversation
Move the specification pin to mdbase-spec main (13531d8), which carries the 0.3.0 release, the type packs and concurrent edits companion profiles, and runtime pack 0.2.1. - import-spec: send remaining repository-relative .md links (release record, rc.5 notes) to GitHub; the v0.2 archive's copied guides stay local. - sync-sources: publish runtime schemas from pack 0.2.1, a superset of 0.2.0 that adds the 1.1.0 record schemas. - runtime page: link the workflow 1.1.0 schema and pack 0.2.1. - Add update-pinned-sources.yml (hourly, dispatch, manual) and merge-pinned-sources.yml so the spec and contracts pins move to main through Site checks without manual bumps.
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
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.
Moves the specification pin from
eabae21(2026-10-03) to mdbase-spec main13531d8, so /spec/ shows the 0.3.0 release: rc.5, rc.6, the 0.3.0 release, and the runtime type-key fix (pack 0.2.1).Changes
site-sources.json: specification ref is now13531d8d2ad7344d45d0eb15124e731e07ee76c4.scripts/import-spec.mjs: the new spec links to repository documents (./release/v0.3.0.md,./docs/releases/0.3.0-rc.5.md) that this site doesn't publish. Those links now go to GitHub, which keeps the link check passing. The v0.2 archive's guides are copied beside it, so their relative links stay as they are.scripts/sync-sources.mjs:/runtime/schemas/v0.2/is now published from pack 0.2.1. Its tree is a strict superset of 0.2.0's: every 1.0.0 file is identical, and it adds the 1.1.0 record schemas.src/pages/runtime/index.astro: the schema and pack links now point at workflow 1.1.0 and pack 0.2.1.update-pinned-sources.yml: runs hourly, on apinned-source-updateddispatch, or manually. When the spec or contracts main branch has moved forward, it opens anautomation/sources-<spec>-<contracts>PR that changes only those refs. A newer run closes an older open PR.merge-pinned-sources.yml: merges that PR once Site checks pass on its exact head. It is guarded on the App author, title, files, and asite-sources.jsondiff limited to the two named refs.Checked locally
13531d8.import-specagainst that build passescheck-linkswith no remaining relative.mdlinks.Site checks runs the full build and test on this PR.