fix: createTool drops version field, uses [skip version], publishable via dispatch#19
Merged
Merged
Conversation
…ia dispatch - buildWouldBeEntry no longer injects the removed per-tool `version` field and now mirrors scaffold/generator.py build_registry_entry exactly (homepage, topics, status, pagesType), so a born repo's catalog entry matches the canonical single source of truth. - Registration commit uses the fleet opt-out `[skip version]` instead of `[skip ci]`, which previously suppressed all CI on the meta PR (so required checks never reported and the API merge blocked). - publish.yml gains workflow_dispatch and an already-published idempotency guard so the package can be published/re-published without depending on a GITHUB_TOKEN release event (which does not trigger downstream workflows). - Bump 0.2.0 -> 0.2.1. Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.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.
Why
The createTool apply path was stale: it injected the removed per-tool
versionfield into registry.json and committed the meta-repo registration with[skip ci](which suppressed ALL CI on the meta PR, so required checks never reported and the API merge blocked). Separately,@tmhs/devtools-mcpwas never actually published — a GITHUB_TOKEN release does not trigger publish.yml'srelease: published.What
buildWouldBeEntryno longer emitsversion; it now mirrors the canonicalscaffold/generator.pybuild_registry_entry(homepage, topics, status, pagesType, type-aware language) so a born repo's catalog entry matches the single source of truth.[skip version](the fleet opt-out) instead of[skip ci].publish.ymlgainsworkflow_dispatch+ an already-published guard so the package can be published idempotently without relying on the broken release-event chain.Build clean; 24 tests pass. No STANDARDS_VERSION/VERSION (meta) change.