Use shared development dependency selection #7
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-block!7
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/owned-ci-source-graph"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
WIP: Select the complete public CI source graphto WIP: Use shared development dependency selectionWIP: Use shared development dependency selectionto Use shared development dependency selectionThe 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.
Pull request closed