Repository navigation
chore: bump dev version to 0.2.0.dev202609181657 - #1280
Merged
Merged
Conversation
potiuk
marked this pull request as ready for review
September 18, 2026 16:58
potiuk
added a commit
that referenced
this pull request
Sep 18, 2026
…ches (#1281) `skills/<name>` is a symlink into the family plugin that owns the skill, so editing a skill changes `plugins/magpie-<family>/skills/<name>/SKILL.md` and leaves the mirror entry an unchanged symlink blob. The workflow's `paths:` filter listed only `skills/**/SKILL.md`, which matches no tracked file in this repository: `git ls-files 'skills/**/SKILL.md'` returns nothing, while all 75 entrypoints sit under `plugins/*/skills/*/SKILL.md`. A filter that matches nothing fails open -- the `measure` job simply never ran on a skill edit. `pre-commit.yml` passes `--skip skill-token-count` because "token measurements run in the path-filtered skill-token-count workflow", so nothing else covered it either, and the generated block in `docs/mode-economics.md` drifted silently. #1278 changed `isolated-setup-doctor/SKILL.md` without regenerating it, and the red check surfaced two PRs later on #1280 -- a dev-version bump whose only qualifying path was `uv.lock`. Add the `plugins/` spelling, matching the `files:` regex the `skill-token-count` hook in `.pre-commit-config.yaml` already carries, and regenerate the one stale row. The new test asserts every measured skill resolves to a path some `paths:` entry matches, so the next family naming scheme cannot quietly fall outside the filter again. Generated-by: Claude Opus 5
Move the dev stamp so adopters' `claude plugin update` picks up the work merged since the previous stamp. The marketplace is served from `main` and the update check compares version strings, so a frozen suffix is a silent no-op: an adopter running that command is told they are already current while sitting behind. Run from the Actions tab by @potiuk. Generated by .github/workflows/bump-dev-version.yml with the documented steps: bump `project.version` in `pyproject.toml`, then `tools/dev/check-family-plugins.py --fix` and `uv lock` to propagate to every manifest. The stamp is UTC at minute resolution. Co-Authored-By: Jarek Potiuk <595491+potiuk@users.noreply.github.com>
potiuk
force-pushed
the
chore/bump-dev-version-35371471907
branch
from
September 18, 2026 17:09
a9abf5d to
bac1dd6
Compare
potiuk
added
family:ci
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 dev stamp to
0.2.0.dev202609181657so adopters'claude plugin updatepicksup the work merged since the previous stamp. The marketplace is served from
mainand the update check compares version strings, so a frozen suffix is asilent no-op — see
docs/setup/marketplace.md.Requested from the Actions tab by @potiuk, who is credited on the commit. The
commit is signed by GitHub and the candidate was checked before this PR was
opened — prek, tests, rat and zizmor all passed in the run that produced it.
Those runs are attached to that workflow run rather than to this PR, so the
required checks here start out unstarted: GitHub raises no events for anything
GITHUB_TOKENdoes. Press Ready for review to start them — that raisesa real event, and the check workflows listen for it.
Opened by
bump-dev-version.yml.