chore(main): release docker-reverse-proxy 0.2.3 - #3221
charlie-e2b merged 3 commits into
Conversation
There was a problem hiding this comment.
LGTM, automated release-please version bump and changelog update.
Extended reasoning...
Overview
This is an automated release-please PR that bumps packages/docker-reverse-proxy from 0.2.2 to 0.2.3 in .release-please-manifest.json and appends the corresponding entry to packages/docker-reverse-proxy/CHANGELOG.md. The changelog entry references PR #3218 ("correct 3 CVES"), which is already merged.
Security risks
None. The changes touch only release metadata (manifest + changelog). No code, config, auth, or crypto is modified.
Level of scrutiny
Minimal. Release-please PRs are mechanical and follow a well-established pattern. The version bump matches the changelog entry, and the referenced commit (076823b) is present in the recent history.
Other factors
No bugs were flagged by the bug hunting system, no reviewer comments are outstanding, and the diff is exactly the shape expected from release-please.
d02671f to
276d8d0
Compare
…docker-reverse-proxy
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b169c2bbe2
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1,5 +1,12 @@ | |||
| # Changelog | |||
|
|
|||
| ## [0.2.3](https://github.com/e2b-dev/infra/compare/docker-reverse-proxy-v0.2.2...docker-reverse-proxy-v0.2.3) (2026-07-08) | |||
There was a problem hiding this comment.
This adds the 0.2.3 changelog entry while .release-please-manifest.json still tracks packages/docker-reverse-proxy at 0.2.2; the release workflow is manifest-driven (.github/workflows/release-please.yml passes that manifest to release-please-action). If this release PR is merged as-is, release-please keeps the docker-reverse-proxy baseline stale after the 0.2.3 release, so the next generated release can be calculated from the wrong previous version instead of 0.2.3.
Useful? React with 👍 / 👎.
…docker-reverse-proxy
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
0.2.3 (2026-07-08)
Bug Fixes
This PR was generated with Release Please. See documentation.