| name | release-version |
| description | Release workflow for eslint-plugin-alias-paths. Use when Codex needs to bump the package version, create the release commit and tag, push them, verify GitHub Actions CI/Release, or check the npm staged publishing state for this repository. |
Release Version
Workflow
Use npm version only with --no-git-tag-version.
Do not use plain npm version patch, because it creates the commit and tag before the required staged diff/content secret scan can run.
- Confirm the worktree is clean.
git status --short
- Confirm the current npm package state.
npm view eslint-plugin-alias-paths version versions --json
- Bump the version without commit/tag side effects.
Default to patch for this 0.0.x package unless the user asks for a different bump:
npm version patch --no-git-tag-version
- Confirm the new version is not already published.
npm view eslint-plugin-alias-paths@<version> version
An E404 result is expected for a new version.
- Run local validation.
pnpm run check
pnpm run publish:dry
- Stage only the release-version files, then run the required scanner.
git add package.json
~/.codex/bin/codex-secret-scan
If additional files changed unexpectedly, inspect them before staging. Do not commit if the scanner fails.
- Check recent commit style and commit with the version as the message.
git log --oneline -5
git commit -m "<version>"
- Create and push the matching tag.
git tag v<version>
git push origin master
git push origin v<version>
- Wait for GitHub Actions.
gh run list --repo mkusaka/eslint-plugin-alias-paths --limit 10 --json databaseId,workflowName,status,conclusion,headSha,url,event,displayTitle
gh run view <run-id> --repo mkusaka/eslint-plugin-alias-paths --json status,conclusion,workflowName,headSha,url,jobs
For a tag release, both CI and Release should pass.
- Check publication state.
The Release workflow uses npm stage publish, so success means the package is staged, not necessarily live on npm. Confirm live state with:
npm view eslint-plugin-alias-paths version dist-tags versions --json
If the new version is still absent, tell the user to approve the staged package on npmjs.com. After approval, re-run the npm view command.
Guardrails
- Use
gh for GitHub operations.
- Do not print, persist, or pass real npm/GitHub tokens.
- Do not write release notes manually unless asked; the workflow uses generated GitHub release notes.
- If a release run creates a GitHub Release but npm is still 404, treat that as normal staged publishing until npm approval is complete.
