chore(deps): bump actions/checkout from 4.3.1 to 6.0.2#4
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump actions/checkout from 4.3.1 to 6.0.2#4dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.3.1 to 6.0.2. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@34e1148...de0fac2) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
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. |
dependabot
Bot
deleted the
dependabot/github_actions/actions/checkout-6.0.2
branch
danafitkowski
added a commit
that referenced
this pull request
May 24, 2026
Fourth-pass ChatGPT audit on v2.9.32 surfaced 19 items. v2.9.33 closes 14 genuinely-shippable items (8 fatal/high audit findings + 6 medium). The remaining 5 are tracked in the new ROADMAP_OPEN.md as either ACCEPTED-LIMITATION (with canned cross-exam responses) or OPEN (roadmap / Dana's action). No more silent open items. FATAL closes - F1 VERIFY_RELEASE.md test-count contradictions (1,071/1,104/1,112) swept to 1,128 across entire file. - F2 release-evidence/v2.9.32/ packet missing — backfilled retroactively from v2.9.32 CI canonical witness; release-evidence/v2.9.33/ will be built as a phase-2 follow-up after CI runs. HIGH closes - #3 SHA sidecar wording reframed as 'gitignored generated artifact' - #4 npm run verify now invokes truncation + version-drift gates; witness JSON records all five gate results - #5 version-refs gate now WARN-by-default, FATAL under CHECK_RELEASE_EVIDENCE=1 (CI / pre-tag hook) - #7 Cases 14/15 moved from validation/p6-comparison/cases/ to validation/engine-limitations/cases/; P6 matrix is now 13 cases - #8 validation/real-xer-corpus/ placeholder folder with full sanitization-checklist documentation MEDIUM closes - #11 docs/jurisdictions.md bottom guarantee section fixed - #12 'No silent wrong-answer paths exist' softened to 'No known silent wrong-answer paths remain on the disclosed validation surface' - #13 DAUBERT disclosure-format paragraph refreshed - #14 Dead-context test replaced with table-driven test that documents emission-path intent for every fatal context + verifies source presence + checks set/docs symmetry - #15 Structured override schema: {rationale, authority_source, analyst, date, exhibit_reference}; legacy string form still accepted with legacy_string_form: true audit flag - #18 README competitor table removed; single-column capability list retained - #19 ROADMAP_OPEN.md added at repo root — machine-readable CLOSED / ACCEPTED-LIMITATION / OPEN categorization for every audit-flagged item OPEN (tracked in ROADMAP_OPEN.md) - #6 P6 column capture (Dana's action) - #8 Real-XER corpus sourcing (Dana's action) - #9 Clean baseline 23 alerts (accepted limitation, Q6 in cross-exam-prep) - #10 1k-10k DAG fixtures (engineering roadmap) - #16 Cryptographic analyst signoff (schema-v2 roadmap) - #17 Machine-readable SOP checklist (schema-v2 roadmap) Engine code - _normalizeForensicStrictOverride() helper added to SECTION Q with backward-compat for string form - _applyForensicStrictValidation() refactored to use normalizer; audit-trail entries carry structured fields + legacy_string_form flag Tests - 1,128 / 1,128 unit tests (+16 from v2.9.32) - 747 / 747 crossval, citation, truncation, version-drift all PASS - npm run verify PASS — witness JSON includes all five gates Engine math byte-identical to v2.9.27-v2.9.32 on non-strict path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Bumps actions/checkout from 4.3.1 to 6.0.2.
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)