Skip to content

chore: release 1.0.0 #44

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
tomek-i merged 1 commit into from
Sep 2, 2026
Merged

chore: release 1.0.0 #44

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
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,12 @@ Releases are automated and should not be cut by hand.

Do not run `pnpm version`, edit the `version` field, or hand-write `CHANGELOG.md` entries for released versions. release-please owns all three.

**`Release-As:` must be the last thing in the commit message.** release-please
reads it as a footer. This repository squash merges, so a pull request with two
commits produces one message with both bodies concatenated, and a footer in the
first commit ends up in the middle where it is ignored. If you need to force a
version, put it in a pull request with a single commit.

**`.github/workflows/release.yml` is load-bearing.** npm trusted publishing is pinned to this repository *and* that exact filename. Renaming the file, or moving the publish step into another workflow, breaks publishing until the trusted publisher on npmjs.com is updated. There is no npm token: authentication is OIDC.

## Gotchas worth knowing
Expand Down