Bump actions/checkout from 4 to 6#16
Merged
Merged
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>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
AnSoFuchs
approved these changes
Apr 30, 2026
ThorFuchs
approved these changes
Apr 30, 2026
3 tasks
ThorFuchs
added a commit
that referenced
this pull request
May 1, 2026
…#24) * feat(site): verify-lane v3.1 — verify-page badges (Lean coverage / mode / bridge) Phase v3.1 of the Verify-Lane release plan. Renders Lean-coverage / mode / bridge-status / scope chips on verify pages. Mirror of the v3.2 result-page enrichment, adapted for verification-domain semantics. Builds on v3.0 (corpus PR #16 + site PR #23) which landed `_data/verify/coverage_by_domain.json`. NEW include: _includes/verify-page-badges.html Reads site.data.verify.coverage_by_domain[page.domain]. Three render branches gated on page.verify_type: - verify_type: domain_verification → Lean coverage chip · verification mode chip · bridge-status chip (Strong ≥ 90% formalized · Moderate ≥ 65% · Emerging otherwise) + optional scope chip → Renders on /verify/domain-verification/{mathematics,physics,life, metaphysics}/ - verify_type: release_manifest → Global TauLib stats · Pinned snapshot · 0 sorries + custom-axiom count → Renders on /verify/release-manifest/ - verify_type: falsification_path | predictions_falsification → Physics-domain Lean linkage · Empirical (2025–2035) mode chip → Renders on /verify/predictions-and-falsification/ Always renders a Public visibility chip first. Layout wiring: _layouts/program-doc.html Calls verify-page-badges.html in the hero block, gated on page.verify_type. Other program-doc consumers (program/, corpus/, etc.) unaffected. Frontmatter updates: /verify/release-manifest.md — added verify_type: release_manifest plus v2_lane / type / status fields for parity with other verify pages. Other 4 domain hubs and predictions-and-falsification already had verify_type set; no frontmatter changes needed. SCSS: _sass/_content.scss .chip-row-verify, .chip-verify-coverage, .chip-verify-mode (formal + empirical variants), .chip-verify-bridge (strong/moderate/emerging variants), .chip-verify-scope. All match the v3.2 chip-row-badges pattern with verify-specific palette. Rendered output verified live (after `bundle exec jekyll build` exit 0): /verify/domain-verification/mathematics/ → Public · Lean · 284 modules · 5002/7617 formalized · Mode · Formal+Empirical · Bridge · Moderate (66%) /verify/domain-verification/physics/ → Public · Lean · 171 modules · 4489/6069 formalized · Mode · Formal+Empirical · Bridge · Moderate (73%) /verify/domain-verification/life/ → Public · Lean · 31 modules · 476/476 formalized · Mode · Formal+Empirical · Bridge · Strong (100%) /verify/domain-verification/metaphysics/ → Public · Lean · 9 modules · 337/337 formalized · Mode · Formal+Empirical · Bridge · Strong (100%) /verify/release-manifest/ → Public · TauLib · 512 modules · 14601 declarations · Mode · Pinned snapshot · 0 sorries · 3 custom axioms /verify/predictions-and-falsification/ → Public · Physics Lean · 171 modules · 4489/6069 formalized · Mode · Empirical (2025–2035) Verification gates (all green): ✓ bundle exec jekyll build → exit 0 in 482s ✓ All 6 chip rows render with v3-aligned classes (data-badge attributes set; v3.2 result-page parity preserved for filterable browse) Sequencing Depends on #23 (v3.0 data file). Already merged. Next phase v3.2 — Domain-verification hub redesign. Expand the 43-60-line thin routing pages into v3-shape hubs with hero stats grid · 5-6 sub-route cards · plain-language intro · See-also footer. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(site): refresh release-manifest sections baseline after v3.1 frontmatter add The v3.1 frontmatter additions to verify/release-manifest.md (verify_type / v2_lane / type / status) shifted the __frontmatter__ section checksum, causing the Registry Verify CI check to fail. This commit regenerates the baseline via `scripts/registry_preserve_prose.py` so the gate passes again. Live + baseline now both: 1fe00850442b307f Verification: ✓ python3 scripts/registry_verify.py --full → All checks passed (dashboard prose / release manifest sections / filter_rules consistency / site data registry totals) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Anna-Sophie Fuchs <anna-sophie.fuchs@panta-rhei.site>
AnSoFuchs
added a commit
that referenced
this pull request
May 1, 2026
Pages "Validate edge headers Worker" build step has been failing on `wrangler deploy --dry-run` since dependabot PR #21 (Bump wrangler from 4.85.0 to 4.87.0) merged. wrangler 4.87 requires Node ≥22.0.0 (per package-lock.json: `"node": ">=22.0.0"`); the workflow uses `actions/setup-node@v4` with `node-version-file: .node-version`, which pinned 20.20.2. Multiple dependabot bump merges (#16 #18 #19 #21) plus PR #27 (σ-polarity + W₃(3) preflight fixes from atlas/audits/site/2026-04-29- preflight-public-outreach/verification-2026-05-01) have queued behind the failing deploy. Bumping `.node-version` to Node 22 LTS unblocks all pending main commits. Choice: 22.11.0 (Node 22 LTS released 2024-10, current at time of writing). Alternative: track the Node 22 line via "22" or "22.x" — chose explicit "22.11.0" for build determinism, matching the prior pattern of pinning a specific patch version. No other Node-version pins exist across the repo (grep -r "node-version" + "20.20.2" + Dockerfile* + .nvmrc returns no matches). package.json has no engines field; package-lock.json's "node": ">=22.0.0" is the wrangler dep requirement that triggered this. Post-merge expectation: Pages workflow re-runs against the current origin/main HEAD; deploy succeeds; the σ-polarity + W₃(3) editorial fixes from PR #27 land live (they're already on origin/main, just not deployed); subsequent `last-modified` timestamp on panta-rhei.site moves forward. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Anna-Sophie Fuchs <anna-sophie.fuchs@panta-rhei.site>
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
2 participants
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)