Skip to content

chore(main): release client-proxy 0.1.0 - #3537

Open
e2b-release-please[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--client-proxy
Open

chore(main): release client-proxy 0.1.0#3537
e2b-release-please[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--client-proxy

Conversation

@e2b-release-please

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.0 (2026-08-05)

Features

  • azure: add azure provider arms to byoc-path build tooling (#1361) (f8fb541)

This PR was generated with Release Please. See documentation.

@cla-bot cla-bot Bot added the cla-signed label Aug 5, 2026
@e2b-release-please
e2b-release-please Bot force-pushed the release-please--branches--main--components--client-proxy branch from 6be2b65 to e71492f Compare August 5, 2026 12:24
@e2b-release-please
e2b-release-please Bot force-pushed the release-please--branches--main--components--client-proxy branch 2 times, most recently from bf85538 to 8132b04 Compare August 5, 2026 12:24

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM — standard Release Please automation bumping client-proxy to 0.1.0.

Extended reasoning...

Overview

This is an auto-generated Release Please PR that bumps the client-proxy package version from 0.0.1 to 0.1.0 in .release-please-manifest.json and appends the corresponding entry to packages/client-proxy/CHANGELOG.md. Both changes are mechanically generated from the already-merged feature commit (#1361, azure provider arms for byoc-path build tooling) and follow the exact same format as prior release-please PRs in this repo.

Security risks

None. No source code, configuration, or infrastructure logic is touched — only version metadata and changelog text.

Level of scrutiny

Minimal scrutiny is warranted. This is a bot-generated, mechanical version/changelog bump with no logic changes, consistent with the standard release-please workflow used throughout this monorepo.

Other factors

No outstanding review comments, no bug findings, and the diff is fully self-contained and reversible (it only affects versioning metadata, not runtime behavior).

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