WIP: fix: refresh generated Cargo locks before cache population #491

Draft
erikinkinen wants to merge 4 commits from feature/generated-cargo-lock-refresh-order into feature/retained-native-library-artifacts
Owner

Locate and verify the actual workspace before clearing its explicitly refreshable generated lock. Dependency-cache population can then resolve the selected providers without first requesting stale revisions. Original source locks remain unchanged.

  • Limit refresh to the actual located workspace lock.
  • Preserve original, intermediate and partial lock evidence.
  • Keep the ordinary no-refresh behavior.
  • Complete CI and dependent host-tool builds.

Stacks on #490.

Locate and verify the actual workspace before clearing its explicitly refreshable generated lock. Dependency-cache population can then resolve the selected providers without first requesting stale revisions. Original source locks remain unchanged. - [x] Limit refresh to the actual located workspace lock. - [x] Preserve original, intermediate and partial lock evidence. - [x] Keep the ordinary no-refresh behavior. - [ ] Complete CI and dependent host-tool builds. Stacks on [#490](https://git.erikinkinen.fi/erix/integration/pulls/490).
erikinkinen added this to the Alpha 1 milestone 2026-11-07 02:31:24 +01:00
fix: Refresh generated Cargo locks before cache population
Some checks failed
CI / host_three (push) Successful in 13m24s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
CI / markdown (push) Successful in 9s
CI / host_two (push) Successful in 18m9s
Coreutils provider graph / coreutils (push) Successful in 2m37s
CI / host_one (push) Failing after 19m43s
CI / rust (push) Successful in 4m0s
CI / integration (push) Has been skipped
CI / host_zero (push) Successful in 7m28s
1ec17bba4c
Locate and verify the actual owned workspace before clearing its explicitly refreshable lock. Cache population can then resolve the selected providers without first requesting stale revisions, while original source locks and unapproved workspace locks remain unchanged.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / host_two (push) Has been cancelled
CI / host_three (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
bb8b1827d1
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Separate Markdown checks from the build workflow
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / host_two (push) Has been cancelled
CI / host_three (push) Has been cancelled
CI / integration (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
Markdown / markdown (push) Has been cancelled
7a57fb0a87
Keep each workflow below the repository size limit by giving Markdown its own file. Preserve event filters, job conditions and command bodies, with independent concurrency for the Markdown workflow.
ci: Use shared development dependency profiles
Some checks failed
Markdown / markdown (push) Successful in 12s
Coreutils provider graph / coreutils (push) Successful in 4m12s
CI / rust (push) Successful in 7m1s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / host_zero (push) Successful in 10m16s
CI / host_three (push) Successful in 19m19s
CI / host_one (push) Failing after 22m58s
CI / host_two (push) Failing after 22m46s
CI / integration (push) Has been skipped
d19288e0af
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
Some checks failed
Markdown / markdown (push) Successful in 12s
Coreutils provider graph / coreutils (push) Successful in 4m12s
CI / rust (push) Successful in 7m1s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / host_zero (push) Successful in 10m16s
CI / host_three (push) Successful in 19m19s
CI / host_one (push) Failing after 22m58s
CI / host_two (push) Failing after 22m46s
CI / integration (push) Has been skipped
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/generated-cargo-lock-refresh-order:feature/generated-cargo-lock-refresh-order'
git switch 'feature/generated-cargo-lock-refresh-order'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/retained-native-library-artifacts'
git merge --no-ff 'feature/generated-cargo-lock-refresh-order'
git switch 'feature/generated-cargo-lock-refresh-order'
git rebase 'feature/retained-native-library-artifacts'
git switch 'feature/retained-native-library-artifacts'
git merge --ff-only 'feature/generated-cargo-lock-refresh-order'
git switch 'feature/generated-cargo-lock-refresh-order'
git rebase 'feature/retained-native-library-artifacts'
git switch 'feature/retained-native-library-artifacts'
git merge --no-ff 'feature/generated-cargo-lock-refresh-order'
git switch 'feature/retained-native-library-artifacts'
git merge --squash 'feature/generated-cargo-lock-refresh-order'
git switch 'feature/retained-native-library-artifacts'
git merge --ff-only 'feature/generated-cargo-lock-refresh-order'
git switch 'feature/retained-native-library-artifacts'
git merge 'feature/generated-cargo-lock-refresh-order'
git push origin 'feature/retained-native-library-artifacts'
Sign in to join this conversation.
No description provided.