Repository navigation
TaskNotes rc.17: leave collections' generator bookkeeping alone - #9
Merged
Merged
Conversation
rc.16's starter added assignees to x-tasknotes-generator.managed_fields. That list follows each collection's field mapping, so any collection with a customized mapping (for example due named deadline) conflicted on it and could not approve TaskNotes. rc.17 publishes rc.12's list unchanged and keeps type version 4, so rc.16 collections upgrade without a version conflict. Starter files are now named by revision; the sync uses the model's TASKNOTES_STARTER_REVISION. A custom-mapping upgrade scenario fails for rc.16 and passes for rc.17. rc.16 is no longer listed. Co-Authored-By: Claude <noreply@anthropic.com>
callumalpass
added a commit
to mdbase-dev/mdbase.dev
that referenced
this pull request
Sep 28, 2026
Pins mdbase-contracts 792c5e74 (mdbase-dev/mdbase-contracts#9). Co-authored-by: Claude <noreply@anthropic.com>
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.
rc.16's starter added
assigneestox-tasknotes-generator.managed_fields. That list follows each collection's field mapping, so any collection with a customized mapping conflicted on it ("Seed upgrade conflicts with customized setting /x-tasknotes-generator/managed_fields") and could not approve TaskNotes. Found by approving TaskNotes App against collections written by TaskNotes 4.13.6, the 5.0 betas and the 5.0 candidate.versionkept at 4 so collections rc.16 already upgraded move to rc.17 without a version conflict.types/tasknotes-task/5.md); the sync uses the model'sTASKNOTES_STARTER_REVISION(Align generated types with the published starter (rc.15) callumalpass/tasknotes-model#19) and writes nothing when run against it.custom-mapping: fails for rc.16, passes for rc.17. rc.16 is no longer listed.Verified on mdbase-rs
88d4a21with Connect's adoption retry: clean rc.12, a generator-written collection with custom colours, both after rc.16, and all 10 TaskNotes 5.0 upgrade outputs (default and custom mappings) approve and keepcancelled.🤖 Generated with Claude Code