Repository navigation
ci: bump discipline action pins from v0.14.4 to v0.18.0 - #218
Merged
Merged
Conversation
Five usages, all pinned to the v0.18.0 release commit (1edfbb8): - ci.yml: Discipline Diff Sentinel, manifest/version-lockstep, archive-contents, and the ci-skip-set gate step - copilot-setup-steps.yml: install-only step for Copilot cloud hooks No workflow logic or inputs change. Validated locally with the v0.18.0 binary: discipline check on this diff passes with 0 errors, 0 warnings, 0 overrides; both workflow YAML files parse. The v0.18.0 ci-integrity gate records this upgrade as a note (discipline-version-changed); from here on, any change that moves the pin to an older release, a movable ref, or a binary source is reported by the Diff Sentinel.
This was referenced Oct 7, 2026
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
1 participant
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.
What
Bumps every pinned
orieg/disciplineaction usage from v0.14.4 (410daf24) to v0.18.0 (1edfbb88— the release-commit SHA for tag v0.18.0, dereferenced from the annotated tag).Five usages across two workflows:
.github/workflows/ci.yml.github/workflows/ci.yml.github/workflows/ci.yml.github/workflows/ci.yml.github/workflows/copilot-setup-steps.ymlNo workflow logic, inputs, or steps change — only the pin + its version comment.
Why
v0.14.4 is four releases old (2026-09-28). v0.15.0 through v0.18.0 (2026-10-06) bring stricter default gates and CI-integrity findings that protect exactly what this repo cares about: workflow exposure of secrets (template-injection, secrets-inherit, checkout-persists-credentials, schedule-trigger-with-secrets), banned actions, unpinned container images, and start-of-migration hardening for the pii/instruction-smuggling/error-swallowing gates.
Validation
discipline check --base origin/main→ PASS (27 gates, 0 errors, 0 warnings, 0 overrides).ci-integritygate reports a discipline-pin upgrade as a note (discipline-version-changed), not a finding — and from this PR onward that gate reports any future change that downgrades the pin, moves it to a movable ref, or switches to a binary source. This upgrade is a note on this run'sci-integritygate.Follow-ups (not in this PR)
comment: trueaction input — post the sentinel report as one always-edited PR comment (needspull-requests: writeon the discipline job).test_reportaction input — wire PHP.phptJUnit output intotest-floorfor runtime test-identity ratcheting.discipline hook install --agent ... --upgrade) so dev/cloud sessions match v0.18.0.