Skip to content

chore: release v0.37.1 - #273

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--unified-api
Open

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

Conversation

@github-actions

Copy link
Copy Markdown

🤖 I have created a release beep boop

0.37.1 (2026-10-30)

Fixed

  • keep credentials written into a project's address out of git errors (ed31e86)

This PR was generated with Release Please. See documentation.

blaipr added a commit that referenced this pull request Oct 30, 2026
Merging the release PR created the tag and the GitHub Release first and
built the image after: for the minutes of the build the new version was
the latest release with no image to pull, and a failed build would have
left a release whose image never existed. (Seen on unified-gitops 0.5.0,
which has the same workflow; fixed there in
OpusProjects/unified-gitops#45.)

- `release-please-config.json`: `"draft": true`. release-please creates
the release as a draft, which has no tag and nobody sees.
- `release.yml`: the publish job checks out the release commit, builds
and pushes the image, and **then** publishes the draft (`gh release edit
--draft=false --latest`), which creates the tag. A failed build leaves a
hidden draft; re-running the job finishes the release.
- `docs/releasing.md` and `CLAUDE.md` describe the new order and the one
approval a release PR needs while `github-actions[bot]` is still a
first-time contributor here (open release PR #273 will need it).
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.

0 participants