Skip to content

fix(projections): support released policy in public projects - #213

Merged
rldyourmnd merged 3 commits into
mainfrom
fix/released-public-project-projections-20261006
Oct 6, 2026
Merged

rldyourmnd merged 3 commits into
mainfrom
fix/released-public-project-projections-20261006

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

An ordinary public project using an immutable policy bundle was rejected unless its anchor also declared the module role. This left public projects without a portable release-based projection path.

Allows released projection sources for any public repository. Private targets still fail before artifact access and must retain their estate policy boundary. Archive/envelope/member validation and template compatibility checks remain in force; existing development and public-module self-projection behavior is unchanged.

Validation: regression test reproduced the public-project rejection before the change; public artifact failure and private-target refusal tests pass. Full go test ./..., 70 Python tests, Go fast validation and shell lint passed. Tests use synthetic repository identities and do not access external providers.

@rldyourmnd
rldyourmnd force-pushed the fix/released-public-project-projections-20261006 branch from 8f51c33 to 7684e05 Compare October 6, 2026 01:01
@rldyourmnd
rldyourmnd merged commit f7f7027 into main Oct 6, 2026
3 checks passed
@rldyourmnd
rldyourmnd deleted the fix/released-public-project-projections-20261006 branch October 6, 2026 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant