Skip Chronicle.Dapr in the common workflow bootstrap - #97
Merged
Conversation
Chronicle.Dapr's publication-boundary governance declares exactly build, preview-publish, and the pinned verify-no-work-records wrapper, with the per-repository extra-allowed policy documents. The bootstrap's added wrappers and its rewrite of the pinned call both violate that boundary, so the repository is skipped rather than fought.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chronicle.Dapr governs its workflows through
tools/verify-workflow-boundary.py: exactly build, preview-publish, and a pinned verify-no-work-records call with repository-specific extra-allowed documents. The bootstrap both adds wrappers it has not adopted and rewrites that pinned call (losing the extras), so main went red after the 2026-09-10 org-wide bootstrap run. Skip the repository instead. No release.