Skip to content

fix(ci): keep PCC standalone after adding provenance workspace #177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 1 commit into from
Nov 6, 2026
Merged

fix(ci): keep PCC standalone after adding provenance workspace #177

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,7 @@ required-features = ["gossamer"]
[workspace]
members = ["crates/provenance"]
default-members = [".", "crates/provenance"]
exclude = ["tools/pcc"]
resolver = "2"

[features]
Expand Down
7 changes: 5 additions & 2 deletions docs/PROVENANCE-EXHIBIT-B.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,8 +113,11 @@ workflows after their owner moved. The selected-actions policy now admits
the full reusable-workflow paths at the existing `metadatastician/standards` revisions
`412a7031577112b31ee287cc6060179d638d6500` and
`e064539116c2dcfdf282a4749dbd58c69961c7e6`, plus the exact third-party action
commits already recorded in `actions.lock`. The admissions were exported
through the canonical Kyaml parser. Existing action allowances and the
commits already recorded in `actions.lock` or in the frozen Rust reusable
workflow at `412a7031577112b31ee287cc6060179d638d6500`. Lockfile admissions
were exported through the canonical Kyaml parser; the reusable workflow's
toolchain/cache commits were checked against that exact revision.
Existing action allowances and the
mandatory SHA-pinning setting are preserved. Admission is not a test receipt;
the actual hosted runs still determine whether the workflows passed.

Expand Down
Loading