Skip to content

chore(main): release 0.7.1#127

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Closed

chore(main): release 0.7.1#127
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.7.1 (2026-05-18)

Bug Fixes

  • ci: use PAT for release-please so tag pushes trigger release.yml (#126) (d6fd9d9)
  • ci: use PAT for release-please so tag pushes trigger release.yml (#98) (81baac9)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot force-pushed the release-please--branches--main branch from d2cf4e1 to b4a066e Compare May 18, 2026 00:31
Copy link
Copy Markdown
Owner

Closing — this proposed v0.7.1 because the merge commit for PR #125 used title "v0.8.0: always-on…" instead of conventional-commit format (feat(serve): …). Release-please reads merge-commit titles for non-squash merges and didn't see a feat: prefix, so it missed the v0.8 always-on work and only counted the fix(ci): PAT patch from #126.

Pushing a chore: bump version with a Release-As: 0.8.0 footer to main so release-please re-proposes the correct v0.8.0 release with the full changelog (always-on + PAT fix). The next PR (#128) will supersede this one.

Process-fix going forward: merge commit titles for non-squash merges need conventional-commit format.


Generated by Claude Code

@dfrostar dfrostar closed this May 18, 2026
@dfrostar dfrostar mentioned this pull request May 18, 2026
2 tasks
dfrostar added a commit that referenced this pull request May 18, 2026
PR #125 (v0.8 always-on) was merged with merge-commit title
"v0.8.0: always-on…" instead of conventional-commit format
(feat(serve): …). release-please reads merge-commit titles for
non-squash merges and missed the feat: prefix, so it proposed v0.7.1
(PR #127, now closed) covering only the fix(ci) PAT patch from PR #126.

The always-on code (/healthz, systemd/launchd templates, always-on.md
walkthrough, RELEASE_NOTES_v0.8.0.md) is already on main. This empty
commit's `Release-As: 0.8.0` footer overrides release-please's version
proposal so the next release-please PR proposes v0.8.0 with the
correct combined changelog (always-on + PAT fix).

Process-fix going forward: merge commit titles for non-squash merges
need conventional-commit format (this PR's own merge title is the
example).

Release-As: 0.8.0

https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ
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