Use shared development dependency selection #7

Closed
erikinkinen wants to merge 2 commits from feature/owned-ci-source-graph into feature/documentation-lint-repair
Owner

Use Integration’s shared branch profile for lib-block CI. Cargo dependencies stay on main; each run records the helper and provider commits for frozen replay.

Keep the source check and guide in Integration, preserving the component’s existing CI commands.

Uses Integration #518.

Use Integration’s shared branch profile for lib-block CI. Cargo dependencies stay on `main`; each run records the helper and provider commits for frozen replay. Keep the source check and guide in Integration, preserving the component’s existing CI commands. Uses [Integration #518](https://git.erikinkinen.fi/erix/integration/pulls/518).
erikinkinen added this to the Alpha 1 milestone 2026-11-07 11:01:25 +01:00
ci: Retain complete public library source graph
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 5s
CI / test (push) Failing after 1m30s
48d2bf87fb
Prepare exact public providers through the maintained original-source gateway while preserving authored main declarations and every original Cargo validation command. Revalidate actual root, complete source set and tracked graph inputs before relying on the prepared consumer.
ci: Use shared development dependency profiles
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / test (push) Successful in 54s
fd69b19573
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.
erikinkinen changed title from WIP: Select the complete public CI source graph to WIP: Use shared development dependency selection 2026-11-07 15:49:47 +01:00
erikinkinen changed title from WIP: Use shared development dependency selection to Use shared development dependency selection 2026-11-13 18:25:21 +01:00
Author
Owner

The current #5 branch already uses Integration’s shared development preparation, verifies the frozen original root and resolved sources, retains the helper/provider snapshot, and keeps Cargo declarations on main. It uses the journal’s explicit companion profile and preserves its native checks. The remaining explicit provider-policy selection is retained in #8’s prepared history. Closing this covered PR to avoid replaying its stale workflow over the current journal work. The source branch is retained.

The current #5 branch already uses Integration’s shared development preparation, verifies the frozen original root and resolved sources, retains the helper/provider snapshot, and keeps Cargo declarations on main. It uses the journal’s explicit companion profile and preserves its native checks. The remaining explicit provider-policy selection is retained in #8’s prepared history. Closing this covered PR to avoid replaying its stale workflow over the current journal work. The source branch is retained.
erikinkinen closed this pull request 2026-11-14 13:46:58 +01:00
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / test (push) Successful in 54s

Pull request closed

Sign in to join this conversation.
No description provided.