Skip to content

chore: release v0.38.0 - #273

Merged
blaipr merged 1 commit into
mainfrom
release-please--branches--main--components--unified-api
Nov 15, 2026
Merged

blaipr merged 1 commit into
mainfrom
release-please--branches--main--components--unified-api

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.38.0 (2026-11-15)

Added

  • show which hosts each sync added and removed (#286) (2d16049)

Fixed

  • deps: update russh to 0.65.0 (#280) (c784aed)
  • keep credentials written into a project's address out of git errors (ed31e86)
  • update crates flagged by RustSec advisories (#285) (061a233)

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).
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--unified-api branch 2 times, most recently from cf1d550 to e4f6abb Compare October 31, 2026 16:37

@blaipr blaipr left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--unified-api branch 2 times, most recently from 5b1037b to e334e82 Compare November 14, 2026 15:54
@github-actions github-actions Bot changed the title chore: release v0.37.1 chore: release v0.38.0 Nov 15, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--unified-api branch from e334e82 to 343fa0f Compare November 15, 2026 00:03
@blaipr
blaipr merged commit 7f8b212 into main Nov 15, 2026
10 checks passed
@blaipr
blaipr deleted the release-please--branches--main--components--unified-api branch November 15, 2026 00:23
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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