一键导入
create-release
Create a new release for ide. Use when the user says "create a release", "new release", "cut a release", or "ship it".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create a new release for ide. Use when the user says "create a release", "new release", "cut a release", or "ship it".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add, gate on, remove, or promote a local feature flag in the ide app. Use when the user says "/feature-flags", "add a feature flag", "put this behind a flag", "remove a flag", "make this always on", "promote a flag to a setting", or "preview feature". The concepts live in docs/development.md; this skill is the step-by-step procedure for each lifecycle operation, including the exact files to touch and the order to touch them.
Analyze a new product or application feature idea, create a reviewable feature analysis artifact, then turn the approved artifact into GitHub backlog issues/PBIs. Use when Gordon invokes "/new-feature", says "new feature", gives a rough feature idea, asks to break down a feature request, or wants feature PBIs/issues created. Do not use for bugfix-only work, release creation, dependency-only maintenance, or direct implementation after an existing issue is already selected.
| name | create-release |
| description | Create a new release for ide. Use when the user says "create a release", "new release", "cut a release", or "ship it". |
Cut a new GitHub release for ide using the versioning and release workflow this
repo expects. Publishing the release triggers the full Build and Test workflow,
which builds, signs, notarizes, and ships the app, so treat this as an
outward-facing action and get it right the first time.
Confirm all of these before creating anything:
main.prod environment, not as a
repo-level secret:
APPLE_IDAPPLE_TEAM_IDAPPLE_APP_PASSWORDDEVELOPER_ID_CERTIFICATEDEVELOPER_ID_PASSWORDHOMEBREW_TAP_DEPLOY_KEYPublish a real release, not a draft, when the user expects the pipeline to run immediately — a draft does not trigger the workflow.
Pull latest:
but clean --pull
Confirm the checkout is clean:
but status -fv
Stop if there are uncommitted or unapplied changes that are not part of the release, and tell Gordon what is dirty.
List existing releases:
gh release list --repo GordonBeeming/ide --limit 10
Determine the next version:
v{major}.{minor}. The release workflow rejects any tag without
the leading v.{major}.{minor}.{github_run_number}
into package.json, src-tauri/tauri.conf.json, and src-tauri/Cargo.toml,
so the packaged app and About dialog carry a valid three-part version based
on the run number.v0.1 unless Gordon asks for another version.Gather the changes since the last release:
LAST_TAG=$(gh release list --repo GordonBeeming/ide --limit 1 --json tagName --jq '.[0].tagName')
git log "${LAST_TAG}..HEAD" --oneline
With no prior release, use:
git log --oneline
Create the release on main. Use a published release (not a draft) when the
user wants the pipeline to start now.
gh release create v{major}.{minor} \
--repo GordonBeeming/ide \
--target main \
--title "v{major}.{minor} - {short description}" \
--notes "$(cat <<'EOF'
# ide v{major}.{minor} - {short description}
## What's new
- {list changes since the last release using git log}
## Install
```bash
brew upgrade --cask gordonbeeming/tap/ide
```
Or download the DMG from the assets below after the release workflow completes.
EOF
)"
The release pipeline then runs on its own:
ide-{version}-aarch64.dmgGordonBeeming/homebrew-tap at Casks/ide.rbWatch the workflow:
gh run list --repo GordonBeeming/ide --workflow "Build and Test" --limit 5
For the relevant run:
gh run watch <run-id> --repo GordonBeeming/ide --exit-status
Report the release URL, workflow run URL, Homebrew cask update status, and any manual follow-up.
v{major}.{minor} (example: v0.2){major}.{minor}.{github_run_number}{major}.{minor}ide-{major}.{minor}-aarch64.dmghttps://github.com/gordonbeeming/ide/releases/download/v#{version.major_minor}/ide-#{version.major_minor}-aarch64.dmgv prefix; never use a patch number in a release tag.prod environment only — do not create
repo-level secrets.DEVELOPER_ID_CERTIFICATE or DEVELOPER_ID_PASSWORD
is missing, report that exact missing secret rather than working around
signing.brew upgrade.