Skip to content

chore(main): release 0.1.4 - #9

Merged
aaronware merged 1 commit into
mainfrom
release-please--branches--main--components--skills
Jul 28, 2026
Merged

chore(main): release 0.1.4#9
aaronware merged 1 commit into
mainfrom
release-please--branches--main--components--skills

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

💎 Automated Release

0.1.4 (2026-07-28)

Miscellaneous 🧹

  • deps: update dependency node to v24 (#7) (c045a11)
  • deps: update googleapis/release-please-action action to v5 (#8) (f34e390)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--skills branch from 63af487 to 55d5b23 Compare July 28, 2026 16:14
@aaronware
aaronware merged commit 793c037 into main Jul 28, 2026
@aaronware
aaronware deleted the release-please--branches--main--components--skills branch July 28, 2026 16:21
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

aaronware added a commit that referenced this pull request Jul 30, 2026
…md (#12)

CLAUDE.md claimed this repo "has no commitlint, husky, release-please, or
Renovate — it's a plain npm package published by hand". Only the commitlint and
husky half was true.

Actually present: release-please (release-please.yml, release-please-config.json,
.release-please-manifest.json) which has cut #6, #9 and #11; Renovate, which has
opened #3, #4, #7 and #8; and an npm publish job authenticating via Trusted
Publishing over OIDC rather than a stored token.

The same section also told maintainers to run npm version and npm publish from
main, which would fight release-please and bypass Trusted Publishing entirely.

An agent reading this would hand-edit package.json and CHANGELOG.md, which is
exactly what commit-and-release forbids, and would not know the PR title is
CI-enforced. That gate matters because squash merges turn the PR title into the
commit message release-please parses, so a malformed title corrupts the
changelog rather than failing loudly.

Also notes that README.md is a release-please extra-files version target, so its
x-release-please markers are not to be touched.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant