Skip to content

chore(main): release docker-reverse-proxy 0.2.3 #3221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
charlie-e2b merged 3 commits into from
Jul 8, 2026
Merged

chore(main): release docker-reverse-proxy 0.2.3 #3221

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
276d8d0
chore(main): release docker-reverse-proxy 0.2.3
e2b-release-please[bot] Jul 8, 2026
b169c2b
Merge branch 'main' into release-please--branches--main--components--…
charlie-e2b Jul 8, 2026
2830915
Merge branch 'main' into release-please--branches--main--components--…
charlie-e2b Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions packages/docker-reverse-proxy/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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)

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Update the release-please manifest with this release

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 👍 / 👎.



### Bug Fixes

* correct 3 CVES ([#3218](https://github.com/e2b-dev/infra/issues/3218)) ([076823b](https://github.com/e2b-dev/infra/commit/076823bc5cbffb9f8c04670c886562445e50ead7))

## [0.2.2](https://github.com/e2b-dev/infra/compare/docker-reverse-proxy-v0.2.1...docker-reverse-proxy-v0.2.2) (2026-07-02)


Expand Down