Skip to content

chore(deps): bump rama-core from 0.3.0-alpha.4 to 0.3.0 in /codex-rs - #565

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/codex-rs/rama-core-0.3.0
Open

chore(deps): bump rama-core from 0.3.0-alpha.4 to 0.3.0 in /codex-rs#565
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/codex-rs/rama-core-0.3.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 11, 2026

Copy link
Copy Markdown
Contributor

Bumps rama-core from 0.3.0-alpha.4 to 0.3.0.

Release notes

Sourced from rama-core's releases.

rama-0.3.0

Rama 0.3.0 is here. This is a big release: the 0.3 series started with the first alpha on 2025-07-07 and carried a long line of protocol work, API redesign, platform hardening, and real-world proxy features all the way to this final release.

For people coming from 0.2: expect breaking changes. The central Context model is gone, service inputs and outputs have been generalized, extensions are now the main way to carry request, response, connection and transport metadata, and Rama owns more of its HTTP and URI surface directly. The migration cost is real, but it buys a cleaner service model, stronger protocol fidelity, better proxy ergonomics, and much more room for the next release trains.

This also closes the long alpha era. From here on we aim to ship regular Rama releases on a 2 to 8 week cadence. Versioning will continue to follow SemVer semantics.

Community

Thank you to everyone who contributed code, reviews, documentation, testing, bug reports, ideas, and production feedback during the 0.3 cycle. This release includes work from Glen De Cauwsemaecker, Brecht Stamper, Abdelkader Boudih, Nicolas Trippar, M-Kusumgar, Ali Tariq, Camille Louédoc-Eyriès, sim-hash, Irfan - ئىرفان, Yukun Wang, hafihaf123, Aydan Pirani, Kenny Lau, MeerKatDev, Maarten Deprez, Dominic Lindsay, Xavier Lambein, Stijn De Clercq, Shabbir Hasan, Antoine Bernardeau, Darshil Patel, Gautham Venkataraman, FS, Elias, Azzam S.A, Nikita, Ian Wagner, bitterpanda, Elizabeth Gonzales Belsuzarri, 0x676e67, KoHcoJlb, and everyone else who helped shape the release.

Thank you also to our GitHub Sponsors for directly funding Rama development, and to our commercial partners for funding a significant part of the work in this cycle. If you want to support Rama, you can become a GitHub Sponsor. If your organisation is looking for a long-term partner around proxies, protocol work, support, training, or custom integrations, see ramaproxy.com.

Alpha Train Recap

  • 0.3.0-alpha.1 (2025-07-07) opened the cycle with the first versions of rama-ws, rama-socks5, rama-unix, built-in Datastar support, SSE work, richer observability, PeetPrint and TLS fingerprinting improvements, protocol peek routing, and a much larger proxy example set.
  • 0.3.0-alpha.2 (2025-08-05) added ACME support, the first rama-crypto crate with JOSE/JWK/JWA/JWS support, connection pooling, TCP connector pools, WebSocket fingerprinting support, target HTTP version enforcement, and the first anti-bot examples.
  • 0.3.0-alpha.3 (2025-08-29) promoted Windows to tier-1, added signed Windows CLI releases and winget packaging, custom X.509 stores, WebSocket extensions, HTTP-to-HTTPS upgrade redirects, include-dir serving, router quality-of-life improvements, and the unified HTTP/SOCKS proxy

... (truncated)

Changelog

Sourced from rama-core's changelog.

0.3.0

Planned release date: 2026-07-07

Rama 0.3.0 is here. This is a big release: the 0.3 series started with the first alpha on 2025-07-07 and carried a long line of protocol work, API redesign, platform hardening, and real-world proxy features all the way to this final release.

For people coming from 0.2: expect breaking changes. The central Context model is gone, service inputs and outputs have been generalized, extensions are now the main way to carry request, response, connection and transport metadata, and Rama owns more of its HTTP and URI surface directly. The migration cost is real, but it buys a cleaner service model, stronger protocol fidelity, better proxy ergonomics, and much more room for the next release trains.

This also closes the long alpha era. From here on we aim to ship regular Rama releases on a 2 to 8 week cadence. Versioning will continue to follow SemVer semantics.

Community

Thank you to everyone who contributed code, reviews, documentation, testing, bug reports, ideas, and production feedback during the 0.3 cycle. This release includes work from Glen De Cauwsemaecker, Brecht Stamper, Abdelkader Boudih, Nicolas Trippar, M-Kusumgar, Ali Tariq, Camille Louédoc-Eyriès, sim-hash, Irfan - ئىرفان, Yukun Wang, hafihaf123, Aydan Pirani, Kenny Lau, MeerKatDev, Maarten Deprez, Dominic Lindsay, Xavier Lambein, Stijn De Clercq, Shabbir Hasan, Antoine Bernardeau, Darshil Patel, Gautham Venkataraman, FS, Elias, Azzam S.A, Nikita, Ian Wagner, bitterpanda, Elizabeth Gonzales Belsuzarri, 0x676e67, KoHcoJlb, and everyone else who helped shape the release.

Thank you also to our GitHub Sponsors for directly funding Rama development, and to our commercial partners for funding a significant part of the work in this cycle. If you want to support Rama, you can become a GitHub Sponsor. If your organisation is looking for a long-term partner around proxies, protocol work, support, training, or custom integrations, see ramaproxy.com.

Alpha Train Recap

  • 0.3.0-alpha.1 (2025-07-07) opened the cycle with the first versions of rama-ws, rama-socks5, rama-unix, built-in Datastar support, SSE work, richer observability, PeetPrint and TLS fingerprinting improvements, protocol peek routing, and a much larger proxy example set.
  • 0.3.0-alpha.2 (2025-08-05) added ACME support, the first rama-crypto crate with JOSE/JWK/JWA/JWS support, connection pooling, TCP connector pools, WebSocket fingerprinting support, target HTTP version enforcement, and the first anti-bot examples.
  • 0.3.0-alpha.3 (2025-08-29) promoted Windows to tier-1, added signed

... (truncated)

Commits
  • 1e094e4 add docsrs-check (just + daily ci) + 0.3.0 notes touch-ups
  • 8ef735d update deps (includes crossbeam security fix)
  • 4f48d82 fix no_std dep leaks in utils/net/core + guard w/ check-nostd
  • 4040ff5 enable serde feature in ipnet (rama-net)
  • 958566a ci: clippy --fix auto-fixes (2026-07-06) (#1060)
  • 37bc64c apple xpc + ne tproxy lifecycle fixes, uri query utils (#1059)
  • 3f6754b update deps + embedded profiles (20260706)
  • 97a8255 ne tproxy: stop callable from async contexts without fault
  • 67b4abe ne tproxy: engine stop bounded even on a wedged runtime
  • aa95355 uri: drop Uri PartialEq<str> impls; compare as_str instead
  • Additional commits viewable in compare view


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Aug 11, 2026
Bumps [rama-core](https://github.com/plabayo/rama) from 0.3.0-alpha.4 to 0.3.0.
- [Release notes](https://github.com/plabayo/rama/releases)
- [Changelog](https://github.com/plabayo/rama/blob/main/CHANGELOG.md)
- [Commits](plabayo/rama@rama-0.3.0-alpha.4...rama-0.3.0)

---
updated-dependencies:
- dependency-name: rama-core
  dependency-version: 0.3.0
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/codex-rs/rama-core-0.3.0 branch from 534fc99 to 91f267b Compare August 12, 2026 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants