Skip to content

docs: RELEASING.md — release process + parked follow-ups (OIDC, CHANGELOG)#5

Open
ionut85 wants to merge 1 commit into
mainfrom
docs/releasing-notes
Open

docs: RELEASING.md — release process + parked follow-ups (OIDC, CHANGELOG)#5
ionut85 wants to merge 1 commit into
mainfrom
docs/releasing-notes

Conversation

@ionut85

@ionut85 ionut85 commented Jun 3, 2026

Copy link
Copy Markdown
Member

Stores the parked follow-ups durably (the dev sandbox is wiped between sessions, so this is the resume bookmark).

docs/RELEASING.md captures:

  • OIDC "Trusted Publishing" plan to automate npm releases — the release.yml workflow + the npmjs.com trusted-publisher setup, so future releases publish from a GitHub Release with no terminal/token. (Priority follow-up.)
  • A CHANGELOG.md todo (entries for 0.1.0 / 0.1.1).
  • The v0.2.0 write-actions item.
  • The manual release checklist + the gotchas we hit on 0.1.1 (orphaned-PR commits, bare npm publish in zsh, scoped --access public, npm propagation lag, tag re-pointing).

No code or runtime changes — docs only. Merge to keep it in the repo, or leave this PR open as the bookmark.


Generated by Claude Code

Captures the OIDC trusted-publishing plan (release.yml + npm setup) to automate
future releases, a CHANGELOG todo, the v0.2.0 write-actions item, and the
manual release checklist + gotchas from the 0.1.1 release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants