Repository navigation
fix: ship tasknotes.task pack 0.3.0-rc.20 - #432
Merged
Merged
Conversation
…s stay installed rc.19 replaced the managed contract at _contracts/tasknotes.task.md without keeping rc.3 and rc.4. A collection whose task type is not the starter and still implements one of those was refused setup as a whole, and TaskNotes showed "Collection setup conflicts" with no way forward. rc.20 (mdbase-contracts#22) is rc.19 plus those two contracts at _contracts/tasknotes.task/<version>.md. Its starter and baselines are unchanged. Vendor it, pin its published URL and digest, and regenerate the manifest.
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.
Why
Opening a collection whose task type is a renamed or customised copy still on
tasknotes.taskrc.3 or rc.4 ended on the terminal "Collection setup conflicts" screen. Pack rc.19 replaces the managed contract at_contracts/tasknotes.task.md(rc.3 to rc.5) and installs nothing for the earlier versions, so the engine refuses the whole plan withdata_contract_version_mismatch.What
tasknotes.taskpack 0.3.0-rc.20 (mdbase-contracts#22, live at mdbase.dev) and pin its URL and digest. It is rc.19 plus the rc.3 and rc.4 contracts at_contracts/tasknotes.task/<version>.md; the starter type and its baselines are unchanged.src/generated/mdbase-app.json(two more contract resources).Checked
pnpm contracts:syncdownloads the published provision and its digest matches the pin.A type still on rc.3 keeps the collection installable but is not one TaskNotes reads; that collection needs its type moved to rc.6 separately.
Merging ships to staging and then production.