chore: ship tasknotes.task pack 0.3.0-rc.18 with every starter baseline - #195
Merged
Merged
Conversation
rc.18 carries the same task starter as rc.17, but its seed lists every earlier published starter (type versions 4, 3, 2 and 1) as `upgrade_from` baselines, so a collection holding any of them gets the reviewed upgrade. The manifest test now asserts the list form and each baseline's digest. The list form needs a Connect release with mdbase-dev/mdbase-connect#567. Co-authored-by: Claude <noreply@anthropic.com>
Merged
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.
Important
Ready: Connect beta125, which includes mdbase-dev/mdbase-connect#567, is in production, and the SDK is published at 0.1.0-beta.125.
What
Ships the
tasknotes.taskpack0.3.0-rc.18published by mdbase-dev/mdbase-contracts@5c06f15. Its task starter is the same as rc.17 (type v4), but the seed'supgrade_fromis now a list naming every earlier published starter: type versions 4, 3, 2 and 1 (per mdbase-spec 05A). A collection seeded from any of them gets the reviewed upgrade.vendor/mdbase-contracts/tasknotes.task-0.3.0-rc.18.json: byte-identical todist/packs/tasknotes.task/0.3.0-rc.18.jsonat contracts5c06f15(replaces rc.17)scripts/canonical-task-pack.mjs: catalog URL, version and digestsha256:9a9ebc26…pinned to rc.18src/generated/mdbase-app.json: regenerated withpnpm manifestscripts/tasknotes-manifest.test.mjs: asserts the pack is rc.18 and that the task seed'supgrade_fromis a list of baselines declaring versions[4, 3, 2, 1], each with a matching digestvendor/README.md,docs/portable-people.md: version referencesNotes
pnpm contracts:syncreturns 404. The vendored file came from the contracts repository directly, and the pinned digest is what the published file must match.@mdbase-dev/connect*packages are pinned to 0.1.0-beta.125, which validates this manifest, including baselines that use YAML anchors (Read baseline identity without alias expansion so anchored starters validate mdbase-dev/mdbase-connect#574).@callumalpass/mdbase0.3.0-rc.8) passes unchanged, so no devDependency bump is needed.Verification
format:check,typecheck,lint,pnpm test(940 passed),pnpm test:release(41 passed, 1 skipped),pnpm test:conformance(core-lite 4982 passed, 1 skipped; mdbase oracle passed).