chore: refresh Cargo.lock for hero_rpc 0.5 → 0.6 development HEAD #131
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_os!131
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_mik_lockfile_refresh_for_hero_rpc_06"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
hero_os failed source-build via hero_builder:
Cargo.lock pinned to 0.5.0 commit of hero_rpc; origin/development now at 0.6.0 (HEAD
01f0030).Fix:
cargo update -p hero_rpc_osisre-pins to current HEAD.Verified GREEN via hero_builder: 5/5 targets built (hero_os, hero_os_server, hero_os_app, hero_os_admin, hero_os_web).
Tracked under lhumina_code/home#230 (P0 source-build sweep).
Signed-off-by: mik-tf
hero_os was failing under hero_builder source-build with: error: failed to select a version for the requirement `hero_rpc_derive = "^0.5.0"` candidate versions found which didn't match: 0.6.0 location searched: Git repository hero_rpc.git?branch=development required by package `hero_rpc_osis v0.5.0` (locked rev 8ba02cbe) Cargo.lock was pinned to a 0.5.0 commit of hero_rpc, but origin/development of hero_rpc is now at 0.6.0 (HEAD 01f0030), breaking transitive resolution. Fix: `cargo update -p hero_rpc_osis` re-pins hero_rpc git deps to current HEAD, refreshing transitive deps to align. Verified GREEN via `~/hero/bin/hero_builder --release --policy-mode warn`: 5/5 targets built (hero_os, hero_os_server, hero_os_app, hero_os_admin, hero_os_web). Tracked under lhumina_code/home#230 (P0 source-build sweep). Signed-off-by: mik-tf