chore(deps): bump actions/checkout from 4 to 6#2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
4 tasks
This was referenced Jun 9, 2026
5 tasks
This was referenced Jun 10, 2026
11 tasks
This was referenced Jun 17, 2026
galuis116
added a commit
to galuis116/vouch
that referenced
this pull request
Jun 19, 2026
…check, fsck coverage - lifecycle.supersede / contradict pre-validate both touched claims via _validate_claim_refs before the first disk write so a legacy dangling ref can't half-apply the operation (P2 vouchdev#3). - proposals.check_approvable dry-runs the put_*-side ref guards via a new _payload_block_reason helper so the default `vouch approve a b` batch flow catches a dangling claim.entities ref BEFORE any write, preserving the all-or-nothing contract (P2 vouchdev#1). - health.fsck reports claim.entities pointing at a missing entity as a new `dangling_claim_entity` error finding, giving operators a preflight repair path for legacy KBs (P2 vouchdev#2).
3 tasks
7 tasks
Tet-9
added a commit
to Tet-9/vouch
that referenced
this pull request
Jul 13, 2026
…dev#428) Adds ClaimType.LESSON and kb.mark_lesson_followed -- an append-only observation of whether a surfaced lesson was actually followed in a given turn. Never edits the claim; appends a lesson.followed audit event with followed, optional context, and claim_type. Registered across all four surfaces: CLI (mark-lesson-followed), MCP (kb_mark_lesson_followed), JSONL (kb.mark_lesson_followed), and capabilities.METHODS. Added to the _STANDARD MCP tool profile alongside kb.confirm, its closest existing analogue. Lessons resurface through the normal retrieval path with no special-casing anywhere in context.py -- verified directly, not assumed. The propose-time repeat guard (vouchdev#147) comes for free: propose_claim already runs find_similar_on_propose for every claim type regardless, so no new code was needed for that acceptance criterion. Not restricted to ClaimType.LESSON: mark_lesson_followed accepts any claim id, matching the issue's own proposed surface ("either a new ClaimType.LESSON or a flag on workflow/warning claims"). Deliberately does not build the "effectiveness computation" system vouchdev#428 names as a downstream consumer (vouchdev#2) -- that reference resolves to an unrelated PR and no such system exists anywhere in this codebase under any name (verified via grep). These events are shaped for such a consumer to exist later; inventing an unspecified analytics system was out of scope. tests/test_lessons.py: 13 tests covering the claim type, retrieval resurfacing, the observe-not-edit invariant, multiple observations, missing- claim handling, the not-restricted-to-LESSON case, registration in capabilities/JSONL/MCP, and the repeat-guard warning.
Tet-9
added a commit
to Tet-9/vouch
that referenced
this pull request
Jul 14, 2026
…dev#428) Adds ClaimType.LESSON and kb.mark_lesson_followed -- an append-only observation of whether a surfaced lesson was actually followed in a given turn. Never edits the claim; appends a lesson.followed audit event with followed, optional context, and claim_type. Registered across all four surfaces: CLI (mark-lesson-followed), MCP (kb_mark_lesson_followed), JSONL (kb.mark_lesson_followed), and capabilities.METHODS. Added to the _STANDARD MCP tool profile alongside kb.confirm, its closest existing analogue. Lessons resurface through the normal retrieval path with no special-casing anywhere in context.py -- verified directly, not assumed. The propose-time repeat guard (vouchdev#147) comes for free: propose_claim already runs find_similar_on_propose for every claim type regardless, so no new code was needed for that acceptance criterion. Not restricted to ClaimType.LESSON: mark_lesson_followed accepts any claim id, matching the issue's own proposed surface ("either a new ClaimType.LESSON or a flag on workflow/warning claims"). Deliberately does not build the "effectiveness computation" system vouchdev#428 names as a downstream consumer (vouchdev#2) -- that reference resolves to an unrelated PR and no such system exists anywhere in this codebase under any name (verified via grep). These events are shaped for such a consumer to exist later; inventing an unspecified analytics system was out of scope. tests/test_lessons.py: 13 tests covering the claim type, retrieval resurfacing, the observe-not-edit invariant, multiple observations, missing- claim handling, the not-restricted-to-LESSON case, registration in capabilities/JSONL/MCP, and the repeat-guard warning.
plind-junior
added a commit
that referenced
this pull request
Jul 16, 2026
…eset - extract verify + arm into a reusable pr-verify.yml shared by the label path and the new slash-command path (avoids github label-recursion). - #2 environment gate: the verify job runs behind a pr-verify environment with a required-reviewer rule, so untrusted head code and the api key are gated on the owner per-run approval. the key is passed explicitly to the handler, not inherited. - #3 comment-command.yml: the owner authorizes a pr by commenting /auto-merge or /verify (owner-gated), as an alternative to the label. - #1 setup_repo_guards.sh replaces setup_branch_protection.sh: creates a branch ruleset (pr + code-owner review + ci/trust-gate checks, org-admin bypass) plus the pr-verify environment and the labels. - deauthorize-on-push now runs on every synchronize (unconditional disarm).
Tet-9
added a commit
to Tet-9/vouch
that referenced
this pull request
Jul 16, 2026
…dev#428) Adds ClaimType.LESSON and kb.mark_lesson_followed -- an append-only observation of whether a surfaced lesson was actually followed in a given turn. Never edits the claim; appends a lesson.followed audit event with followed, optional context, and claim_type. Registered across all four surfaces: CLI (mark-lesson-followed), MCP (kb_mark_lesson_followed), JSONL (kb.mark_lesson_followed), and capabilities.METHODS. Added to the _STANDARD MCP tool profile alongside kb.confirm, its closest existing analogue. Lessons resurface through the normal retrieval path with no special-casing anywhere in context.py -- verified directly, not assumed. The propose-time repeat guard (vouchdev#147) comes for free: propose_claim already runs find_similar_on_propose for every claim type regardless, so no new code was needed for that acceptance criterion. Not restricted to ClaimType.LESSON: mark_lesson_followed accepts any claim id, matching the issue's own proposed surface ("either a new ClaimType.LESSON or a flag on workflow/warning claims"). Deliberately does not build the "effectiveness computation" system vouchdev#428 names as a downstream consumer (vouchdev#2) -- that reference resolves to an unrelated PR and no such system exists anywhere in this codebase under any name (verified via grep). These events are shaped for such a consumer to exist later; inventing an unspecified analytics system was out of scope. tests/test_lessons.py: 13 tests covering the claim type, retrieval resurfacing, the observe-not-edit invariant, multiple observations, missing- claim handling, the not-restricted-to-LESSON case, registration in capabilities/JSONL/MCP, and the repeat-guard warning.
Tet-9
added a commit
to Tet-9/vouch
that referenced
this pull request
Jul 17, 2026
…dev#428) Adds ClaimType.LESSON and kb.mark_lesson_followed -- an append-only observation of whether a surfaced lesson was actually followed in a given turn. Never edits the claim; appends a lesson.followed audit event with followed, optional context, and claim_type. Registered across all four surfaces: CLI (mark-lesson-followed), MCP (kb_mark_lesson_followed), JSONL (kb.mark_lesson_followed), and capabilities.METHODS. Added to the _STANDARD MCP tool profile alongside kb.confirm, its closest existing analogue. Lessons resurface through the normal retrieval path with no special-casing anywhere in context.py -- verified directly, not assumed. The propose-time repeat guard (vouchdev#147) comes for free: propose_claim already runs find_similar_on_propose for every claim type regardless, so no new code was needed for that acceptance criterion. Not restricted to ClaimType.LESSON: mark_lesson_followed accepts any claim id, matching the issue's own proposed surface ("either a new ClaimType.LESSON or a flag on workflow/warning claims"). Deliberately does not build the "effectiveness computation" system vouchdev#428 names as a downstream consumer (vouchdev#2) -- that reference resolves to an unrelated PR and no such system exists anywhere in this codebase under any name (verified via grep). These events are shaped for such a consumer to exist later; inventing an unspecified analytics system was out of scope. tests/test_lessons.py: 13 tests covering the claim type, retrieval resurfacing, the observe-not-edit invariant, multiple observations, missing- claim handling, the not-restricted-to-LESSON case, registration in capabilities/JSONL/MCP, and the repeat-guard warning.
Tet-9
added a commit
to Tet-9/vouch
that referenced
this pull request
Jul 17, 2026
…dev#428) Adds ClaimType.LESSON and kb.mark_lesson_followed -- an append-only observation of whether a surfaced lesson was actually followed in a given turn. Never edits the claim; appends a lesson.followed audit event with followed, optional context, and claim_type. Registered across all four surfaces: CLI (mark-lesson-followed), MCP (kb_mark_lesson_followed), JSONL (kb.mark_lesson_followed), and capabilities.METHODS. Added to the _STANDARD MCP tool profile alongside kb.confirm, its closest existing analogue. Lessons resurface through the normal retrieval path with no special-casing anywhere in context.py -- verified directly, not assumed. The propose-time repeat guard (vouchdev#147) comes for free: propose_claim already runs find_similar_on_propose for every claim type regardless, so no new code was needed for that acceptance criterion. Not restricted to ClaimType.LESSON: mark_lesson_followed accepts any claim id, matching the issue's own proposed surface ("either a new ClaimType.LESSON or a flag on workflow/warning claims"). Deliberately does not build the "effectiveness computation" system vouchdev#428 names as a downstream consumer (vouchdev#2) -- that reference resolves to an unrelated PR and no such system exists anywhere in this codebase under any name (verified via grep). These events are shaped for such a consumer to exist later; inventing an unspecified analytics system was out of scope. tests/test_lessons.py: 13 tests covering the claim type, retrieval resurfacing, the observe-not-edit invariant, multiple observations, missing- claim handling, the not-restricted-to-LESSON case, registration in capabilities/JSONL/MCP, and the repeat-guard warning.
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.
Bumps actions/checkout from 4 to 6.
Release notes
Sourced from actions/checkout's releases.
... (truncated)
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
de0fac2Fix tag handling: preserve annotations and explicit fetch-tags (#2356)064fe7fAdd orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set (...8e8c483Clarify v6 README (#2328)033fa0dAdd worktree support for persist-credentials includeIf (#2327)c2d88d3Update all references from v5 and v4 to v6 (#2314)1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)08c6903Prepare v5.0.0 release (#2238)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)