Use shared development dependency selection #28

Closed
erikinkinen wants to merge 7 commits from feature/public-ci-source-graph into feature/native-receipt-fixture-correlation
Owner

Use Integration’s shared branch profile for sha2-tool 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.

Depends on #27.

Use Integration’s shared branch profile for sha2-tool 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). Depends on [#27](https://git.erikinkinen.fi/erix/sha2-tool/pulls/27).
erikinkinen added this to the Alpha 1 milestone 2026-11-07 10:52:16 +01:00
ci: Select the public dependency 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 30s
d6aa571d03
Keep authored dependencies on main while explicitly selecting the public
feature providers needed by this component. Retain the actual source
consumer and check its revision and tracked graph before the original
build, documentation and test commands.
ci: Declare the complete source repository set
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / test (push) Failing after 1m51s
c351e4495a
Include every selected provider in the explicit repository catalog so
the graph can admit its original sources. Keep fixture build helpers
separate from dependency preparation where their APIs differ.
ci: Retain the current dependency preparation and command owner
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
CI / test (push) Failing after 2m5s
a8fb828f21
Use the maintained catalog-provider preparation to refresh stale lock
selections against the explicit public sources. Check precisely the
actual resolved source set, and retain the original native profile and
cleanup gates with the current command owner.
ci: Retain the current dependency preparation and command owner
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 10s
CI / test (push) Failing after 2m26s
438deb51ed
Use the maintained catalog-provider preparation to refresh stale lock
selections against the explicit public sources. Check precisely the
actual resolved source set, and retain the original native profile and
cleanup gates with the current command owner.
ci: Retain the current dependency preparation and command owner
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 7s
CI / test (push) Successful in 3m35s
110a173446
Use the maintained catalog-provider preparation to refresh stale lock
selections against the explicit public sources. Check precisely the
actual resolved source set, and retain the original native profile and
cleanup gates with the current command owner.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Has been cancelled
CI / markdown (push) Has been cancelled
588caa8bcd
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 ci: Select the public dependency source graph to Use shared development dependency selection 2026-11-07 15:51:39 +01:00
ci: Declare policy helper and output boundaries
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 7s
CI / test (push) Successful in 3m20s
5db5db4671
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Author
Owner

The complete tree in this PR is already present on feature/native-receipt-fixture-correlation at d6c81b887b7e3c4d71e2ce79605103cbe7b9541e. This includes the shared development profile and removal of the copied source check and guide. Closing as covered to avoid duplicating those commits; the source branch is retained.

The complete tree in this PR is already present on `feature/native-receipt-fixture-correlation` at `d6c81b887b7e3c4d71e2ce79605103cbe7b9541e`. This includes the shared development profile and removal of the copied source check and guide. Closing as covered to avoid duplicating those commits; the source branch is retained.
erikinkinen closed this pull request 2026-11-14 18:28:01 +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 7s
CI / test (push) Successful in 3m20s

Pull request closed

Sign in to join this conversation.
No description provided.