Repository navigation
docs(issues): add the ISSUE-717 page and the per-trigger cache resolution - #432
Merged
Merged
Conversation
…tion plumber PR #500 (issue #497) teaches releaseWorkflowsMustNotRestoreUntrustedCache to resolve release context per trigger and adds ISSUE-717, the medium verify-manually variant for enable expressions it cannot resolve. This adds the ISSUE-717 registry entry (its DocURL target) and updates the ISSUE-705 remediation and tips: the conditional enable form and if-gated caching steps are now sanctioned remediations the analyzer proves, and unresolvable expressions downgrade instead of asserting the High. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ft8dmcMLK7V9XZh7JX4vzs
|
Preview deployment for 4af6ddd: https://getplumber-k5dctwadw-getplumber.vercel.app |
…bes the per-trigger resolution The controls-configuration reference ended the cache control with ISSUE-705 alone; it now names ISSUE-717 too and says that job and step conditions are resolved per trigger. The control description on the issue pages gains the publish-script release context and the per-trigger clause, and the ISSUE-717 description covers the default-mode disable input the rule also downgrades (aligned with the CLI's codes.go wording). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ft8dmcMLK7V9XZh7JX4vzs
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.
Companion to getplumber/plumber#500 (fixes plumber#497). Merge AFTER the CLI release that carries it, so the ISSUE-717 DocURL resolves the moment the code can be emitted.
ISSUE-717registry entry: conditional cache on a release path that Plumber cannot resolve per trigger (medium, verify manually), with bad/good examples (thevars.*expression vs the canonicalgithub.event_name != '<publish trigger>' && '<manager>' || ''form) and tips covering the resolvable shapes, default-mode disable inputs, and reusable workflows.ISSUE-705updated: the remediation now names the conditional enable form and if-gated caching steps as proven remediations, a tip explains the per-trigger resolution, andISSUE-717joins its related codes.Registry-only change (
src/data/issues.ts); the page is generated. Verified the file parses (esbuild); relying on CI for the full build per the usual local OOM.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ft8dmcMLK7V9XZh7JX4vzs