Update dependencies to target main branch and address archived hero_login crate #16

Open
opened 2026-06-08 11:12:51 +00:00 by nabil_salah · 0 comments
Member

Background

As part of our overarching goal to stabilize repositories for production (as outlined in repos_focus_production.md), we need to ensure that our crate dependencies are pointing to stable production branches.

Current Problem

Currently, the Cargo.toml in hero_onboarding has two main issues:

  1. Branch Mismatch: Dependencies are still pointing to the development branch instead of the main branch.
  2. Archived Dependency: We are currently depending on hero_login, which has been archived and is no longer maintained.

Action Items

  • Update all internal dependency git references in Cargo.toml to use branch = "main".
  • Investigate the usage of the archived hero_login crate.
  • Either replace hero_login with its active successor or refactor the code to remove the dependency entirely.
  • Run cargo check, cargo update and cargo test to ensure the onboarding flow builds successfully with the updated dependencies.
### Background As part of our overarching goal to stabilize repositories for production (as outlined in [`repos_focus_production.md`](https://forge.ourworld.tf/lhumina_code/home/src/branch/development/repos_focus_production.md)), we need to ensure that our crate dependencies are pointing to stable production branches. ### Current Problem Currently, the `Cargo.toml` in `hero_onboarding` has two main issues: 1. **Branch Mismatch:** Dependencies are still pointing to the `development` branch instead of the `main` branch. 2. **Archived Dependency:** We are currently depending on [`hero_login`](https://forge.ourworld.tf/lhumina_research/hero_login), which has been archived and is no longer maintained. ### Action Items - [ ] Update all internal dependency git references in `Cargo.toml` to use `branch = "main"`. - [ ] Investigate the usage of the archived `hero_login` crate. - [ ] Either replace `hero_login` with its active successor or refactor the code to remove the dependency entirely. - [ ] Run `cargo check`, `cargo update` and `cargo test` to ensure the onboarding flow builds successfully with the updated dependencies.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_onboarding#16
No description provided.