chore(workspace): bump to 0.6.0 to cohere with hero_proc / hero_rpc / hero_lib #49

Closed

mik-tf wants to merge 1 commit from development_workspace_06_lift into development

mik-tf commented

2026-05-08 22:01:39 +00:00

Owner

Summary

Bumps the hero_proxy workspace from 0.5.0 to 0.6.0 to cohere with the rest of the Hero stack on development (hero_proc, hero_rpc, hero_lib already at 0.6.0).

Why

hero_proxy_sdk's Cargo.toml declares hero_rpc_derive = "^0.5.0" against branch = "development". Cargo resolves that branch source freshly to the current HEAD, finds 0.6.0, and refuses to satisfy ^0.5.0. The error fires on any cargo update -p hero_proc_sdk because hero_proc's previously locked SHA was force-pushed and partially GC'd, forcing cargo into a re-resolution.

What changes

[workspace.package] version: 0.5.0 to 0.6.0
4 hero git deps (hero_proc_sdk / hero_service / hero_rpc_derive / hero_rpc_openrpc) to 0.6.0
herolib_core to 0.6.0
Cargo.lock regenerated (+282 / -123 lines, mostly transitive rustls-platform-verifier + reqwest 0.13 additions pulled by the upstream rustls swap)

version.workspace = true cascades to all sub-crates.

Verification

cargo build --release clean across the full workspace against 0.6.0 upstream — no API breakage.
Unit tests pass.
6 pre-existing integration test failures (test_proxy_routing_*, test_full_lifecycle) reproduce identically on development pre-bump — unrelated axum::ConnectInfo<SocketAddr> extension wiring issue, out of scope for this PR.

Closes

Closes #48

## Summary Bumps the hero_proxy workspace from 0.5.0 to 0.6.0 to cohere with the rest of the Hero stack on `development` (hero_proc, hero_rpc, hero_lib already at 0.6.0). ## Why `hero_proxy_sdk`'s `Cargo.toml` declares `hero_rpc_derive = "^0.5.0"` against `branch = "development"`. Cargo resolves that branch source freshly to the current HEAD, finds 0.6.0, and refuses to satisfy `^0.5.0`. The error fires on any `cargo update -p hero_proc_sdk` because hero_proc's previously locked SHA was force-pushed and partially GC'd, forcing cargo into a re-resolution. ## What changes - `[workspace.package] version`: 0.5.0 to 0.6.0 - 4 hero git deps (hero_proc_sdk / hero_service / hero_rpc_derive / hero_rpc_openrpc) to 0.6.0 - herolib_core to 0.6.0 - `Cargo.lock` regenerated (+282 / -123 lines, mostly transitive rustls-platform-verifier + reqwest 0.13 additions pulled by the upstream rustls swap) `version.workspace = true` cascades to all sub-crates. ## Verification - `cargo build --release` clean across the full workspace against 0.6.0 upstream — no API breakage. - Unit tests pass. - 6 pre-existing integration test failures (`test_proxy_routing_*`, `test_full_lifecycle`) reproduce identically on `development` pre-bump — unrelated `axum::ConnectInfo<SocketAddr>` extension wiring issue, out of scope for this PR. ## Closes Closes https://forge.ourworld.tf/lhumina_code/hero_proxy/issues/48

mik-tf added 1 commit

2026-05-08 22:01:39 +00:00

chore(workspace): bump to 0.6.0 to cohere with hero_proc / hero_rpc / hero_lib

Build & Test / check (push) Failing after 2s

Details

Build & Test / check (pull_request) Failing after 3s

Details

9fe36d4118

hero_proc, hero_rpc and hero_lib have all bumped their workspace versions
to 0.6.0 on `development`. hero_proxy was still on 0.5.0, with
`hero_proxy_sdk` declaring `hero_rpc_derive = "^0.5.0"` against
`branch = "development"` — so any downstream cargo update against fresh
upstream re-resolved the source to 0.6.0 and failed the ^0.5.0 constraint.

Bumps the workspace package version and the four hero_* git
dependencies (hero_proc_sdk, hero_service, hero_rpc_derive,
hero_rpc_openrpc, herolib_core) to 0.6.0. `version.workspace = true`
sub-crates inherit automatically.

Verified: full workspace `cargo build --release` succeeds against the
0.6.0 upstream surface (no API breakage). Unit tests pass; the 6
`hero_proxy_tests::integration::test_proxy_routing_*` /
`test_full_lifecycle` failures with `Missing request extension:
ConnectInfo<SocketAddr>` reproduce identically on `development`
pre-bump and are unrelated (axum extension wiring, out of scope).

Closes #48

mik-tf commented

2026-05-09 00:11:01 +00:00

Author

Owner

Superseded by upstream commit f9a252d2 on development (2026-05-09T02:02:47, "fix: bump hero_proxy to v0.6.0, align hero_rpc/hero_proc/herolib_core deps to 0.6.0"), which lands the identical six-line Cargo.toml bump this PR proposed. Cargo.toml content is byte-identical between this branch and development; the only divergence is a regenerable Cargo.lock. Closing — no diff left to take.

Closes #48

Superseded by upstream commit `f9a252d2` on `development` (2026-05-09T02:02:47, "fix: bump hero_proxy to v0.6.0, align hero_rpc/hero_proc/herolib_core deps to 0.6.0"), which lands the identical six-line Cargo.toml bump this PR proposed. `Cargo.toml` content is byte-identical between this branch and `development`; the only divergence is a regenerable `Cargo.lock`. Closing — no diff left to take. Closes https://forge.ourworld.tf/lhumina_code/hero_proxy/issues/48