Skip to content

docs: refresh CLAUDE.md #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roquerodrigo merged 1 commit into from
Sep 7, 2026
Merged

docs: refresh CLAUDE.md #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,9 +63,9 @@ release-please/publish rely on.
- Versioning and `CHANGELOG.md` are fully owned by `release-please`
(Conventional Commits parsed from `main`). Don't hand-edit
`package.json`'s `version`.
- **No CI step publishes to npm.** `release.yml` only runs `release-please`
(version bump + tag + GitHub release); someone still has to run
`npm publish` locally afterward (`prepack`/`prepublishOnly` build and
verify it). This has drifted before (tags/`CHANGELOG.md` ahead of what's
on npm) — check `npm view fitdays-api version` against `package.json`
before assuming a release shipped.
- **Publishing to npm is automated.** `release.yml` runs `release-please`
(version bump + tag + GitHub release), then a `publish` job fires only when
`release-created == 'true'` and pushes to npm via trusted publishing (OIDC,
`id-token: write` — no stored registry token). The `workflow_run.event ==
'push'` guard is what stops a green-CI PR from cutting a release.
`prepack`/`prepublishOnly` build and verify the package before it ships.