chore: add tag-driven release workflow and community health files - #4
Conversation
- .github/workflows/release.yml: on vX.Y.Z tag push, run the full check gate, npm publish with provenance (NPM_TOKEN secret), and create the GitHub Release from the matching CHANGELOG section - CONTRIBUTING.md: dev setup, check gate, spec-driven workflow, layout conventions, PR expectations, and the release runbook - SECURITY.md: private reporting via GitHub Security Advisories, token handling scope notes - Issue forms (bug/feature), issue config links, PR template Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f44df0f59d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - name: Create GitHub Release from CHANGELOG | ||
| run: | |
There was a problem hiding this comment.
When a release tag has no matching nonempty ## X.Y.Z section—for example, because the version was bumped but the changelog was missed—this validation runs only after npm publish has permanently published that name/version. The job then exits without creating the GitHub Release, and rerunning stops at the already-published version; extract and validate the notes before publishing, and ideally make already-published reruns idempotent.
AGENTS.md reference: AGENTS.md:L89-L89
Useful? React with 👍 / 👎.
| `YUQUE_TOKEN`, or `YUQUE_PERSONAL_TOKEN`. Tokens are only ever sent to the | ||
| configured Yuque host (`https://www.yuque.com` by default, or the host you | ||
| set via `--host` / `YUQUE_HOST`) as the `X-Auth-Token` header. |
There was a problem hiding this comment.
When the configured API endpoint returns a cross-origin 3xx response, Axios follows it by default, while src/client/http.ts:38-46 sets X-Auth-Token globally without disabling redirects or stripping that custom header before redirecting. Consequently, the token can be forwarded beyond the configured host, contradicting this absolute security guarantee; either enforce same-origin redirects in the HTTP client or qualify the documentation.
Useful? React with 👍 / 👎.
1 participant
Release engineering + community infrastructure:
vX.Y.Ztag runs the fullnpm run checkgate, verifies the tag matchespackage.json, publishes to npm with provenance, and creates the GitHub Release from the matching CHANGELOG section. Requires theNPM_TOKENrepo secret (npm automation token) — one-time setup.No runtime code changes.
🤖 Generated with Claude Code