releasing
Use when asked to release, publish or tag a plugin or the Bifrost framework in this repository, to bump versions, push release tags (<mod>-v*, framework-v*), or when a Release Plugins / Publish Bifrost Framework run on GitHub failed.
- License 许可
- MIT
- 最近更新
- 2026-10-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- releasing
- description
- Use when asked to release, publish or tag a plugin or the Bifrost framework in this repository, to bump versions, push release tags (<mod>-v*, framework-v*), or when a Release Plugins / Publish Bifrost Framework run on GitHub failed.
03 SKILL.md 正文
Releasing plugins and the framework
Core principle: a tag is a public, irreversible trigger. CI runs on a clean checkout that differs from
this machine (no types/engine, no dist, no node_modules, Linux, bun install), so local green is
not proof. Prove the release on a clean clone and with the workflows accepted before any tag leaves
the machine.
What ships where
| Target | Version lives in | Tag | Workflow | Result |
|---|---|---|---|---|
plugin <mod> |
version in plugins/<mod>/src/plugin.tsx |
<mod>-v<version> |
release-plugins.yml |
orphan branch release/<mod> |
| framework | packages/bifrost/package.json + ## <version> in its CHANGELOG.md |
framework-v<version> |
publish-framework.yml |
@gidragir/bifrost on GitHub npm |
.claude-plugin/marketplace.json points at release/<mod> and carries each plugin's version.
Procedure
- Bump. Every target whose files changed since its last tag gets a new version (
git tag -l '<mod>-v*'). Framework: moveUnreleasedinCHANGELOG.mdinto## <version>. Plugins:pnpm marketplace. - Commit. One scope per commit (
feat(bifrost),feat(<mod>),build,ci), then the release commit (release: <mod> <version>, …) last: fixes found later go before a new release commit, not after it. pnpm release:checkuntil it printsReady. It replays the CI steps on a clean clone of HEAD, checks versions against tags, the CHANGELOG section and marketplace.json, and runs actionlint when installed. It prints the tags to push.- Push
mainalone, wait ~20 s,gh run list -L 5. A run that failed in 0 s with "This run likely failed because of a workflow file issue" means GitHub rejected a workflow: fix it, back to step 3. - Push the tags printed in step 3 (
git tag -a <tag> -m …,git push origin <tags>). - Verify the result, not the run:
- plugin:
gh api "repos/gidragir/claude-mods/contents/.claude-plugin/plugin.json?ref=release/<mod>" --jq .content | base64 -dshows the new version; - framework:
gh run view <id> --log | grep "+ @gidragir/bifrost@".
- plugin:
When a release run fails after the tags are pushed
Do not move, delete or re-push a tag. Fix on main, run pnpm release:check, push main, then rebuild
from main: gh workflow run release-plugins.yml -f plugin=<mod> or gh workflow run publish-framework.yml.
Tell the user the release was built from main, not from the tag.
Known CI traps
| Symptom | Cause |
|---|---|
build.mjs: Cannot find module 'claude-code' |
engine types are local only; the build must not need types/engine |
| run fails in 0 s, "workflow file issue" | invalid workflow, e.g. matrix.* in a job-level if |
with: gets the literal $VAR |
with: takes ${{ env.VAR }}, not shell variables |
a step reads repo files before actions/checkout |
order of steps |
Red flags: stop
- "Tests pass locally, tag it": run
pnpm release:check. - Pushing
mainand tags in one command. - "The run is green": check the release branch or the published version.
- Re-pointing a pushed tag to "fix" a release.
04 同仓库更多 Skills
__MOD_NAME__
__MOD_DESCRIPTION__
cross-mod
Hub for building plugins that run in both Claude Code and Google Antigravity (agy) with the Bifrost framework. Use when starting any plugin work in this repository to find the right specialized skill and the end-to-end workflow.
ref-pane
Inspect and navigate project artifact references (such as RV-1, FB-2, T-3, ADR-4) in the Auxiliary Pane.
bifrost-dev
Use when changing @gidragir/bifrost itself (packages/bifrost) - adding or renaming an export, Host member, primitive or component, changing codegen or the adapters, bumping its version or releasing it - and not when building a plugin under plugins/<mod>.
bifrost-claude-adapter
Use when changing packages/bifrost/src/claude or src/cli codegen, or when a generated hooks module fails claude plugin validate/test for a reason the framework (not the plugin) causes - scanner errors, missing state contract keys, guard hooks, next(e) chaining.
bifrost-agy-adapter
Use when changing packages/bifrost/src/agy - the generated Antigravity aux-pane server, page runtime client.js, effects, token and preload contract, HTML renderer or bifrost.css - or when an agy pane misbehaves for every plugin rather than one.