Summary
Add a shared environment version manifest or lock file that both pypto and pypto-lib can consume, so dependency and toolchain upgrades are defined in one place and stay synchronized.
Motivation / Use Case
Environment-related versions currently need to be maintained separately across pypto and pypto-lib. This makes coordinated upgrades error-prone and increases the risk of drift between local development, CI, and issue-reproduction workflows.
A shared source of truth for environment versions would reduce duplicated maintenance, make upgrades easier to roll out consistently, and improve reproducibility across the two repositories.
Proposed API / Behavior
Introduce a shared environment version manifest (or equivalent single-source configuration) that is reused by both repositories.
Expected behavior:
- Environment and toolchain versions are declared in one place.
- Setup and CI flows in both
pypto and pypto-lib read from the same configuration.
- Upgrading the environment only requires updating the shared manifest, rather than changing multiple repositories independently.
Alternatives Considered
Continue maintaining separate environment configuration in each repository and manually keep them in sync during upgrades.
Additional Context
This would also help contributor onboarding and issue reproduction, because both repositories could rely on the same environment definition instead of duplicating version management.
Summary
Add a shared environment version manifest or lock file that both
pyptoandpypto-libcan consume, so dependency and toolchain upgrades are defined in one place and stay synchronized.Motivation / Use Case
Environment-related versions currently need to be maintained separately across
pyptoandpypto-lib. This makes coordinated upgrades error-prone and increases the risk of drift between local development, CI, and issue-reproduction workflows.A shared source of truth for environment versions would reduce duplicated maintenance, make upgrades easier to roll out consistently, and improve reproducibility across the two repositories.
Proposed API / Behavior
Introduce a shared environment version manifest (or equivalent single-source configuration) that is reused by both repositories.
Expected behavior:
pyptoandpypto-libread from the same configuration.Alternatives Considered
Continue maintaining separate environment configuration in each repository and manually keep them in sync during upgrades.
Additional Context
This would also help contributor onboarding and issue reproduction, because both repositories could rely on the same environment definition instead of duplicating version management.