build(deps): Bump actions/checkout from 4 to 6 - #209
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>
dependabot
Bot
added
dependencies
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. |
dependabot
Bot
deleted the
dependabot/github_actions/actions/checkout-6
branch
November 25, 2025 14:49
joelteply
added a commit
that referenced
this pull request
Jun 9, 2026
…reakage from layout sweep (#1562) The layout sweep (PR #1557, task #214) moved `generate-config.ts` from `src/generator/` to `tools/generator/`. Node's module resolution walks ancestors of the SCRIPT location, not `process.cwd()`, so the `import * as dotenv from 'dotenv'` at the top now traverses `tools/generator/` -> `tools/` -> `/` looking for `node_modules/dotenv` and finds nothing — `dotenv` only exists at `src/node_modules/dotenv` (a SIBLING of `tools/`, not an ancestor). Every TS-validation CI job that invokes `npx tsx ../tools/generator/generate-config.ts` has been failing on canary since the layout sweep merged: Error: Cannot find module 'dotenv' Require stack: - /home/runner/work/continuum/continuum/tools/generator/generate-config.ts Surfaced via PR #1561's validate / ts-eslint-baseline-ratchet / verify-architectures / verify-after-rebuild checks. NOT caused by that PR's diff — pre-existing canary infra regression that has been silently breaking every TS PR check since the layout sweep landed. Fix: replace `dotenv.parse()` with a 15-line inline `parseEnvText`. The script only ever called `.parse()` (the pure string-to-KV transform), never the `.config()` side-effect path that mutates process.env. Inline parser handles the same shape (KEY=value, optional surrounding quotes, # comments, blank lines). Like-for-like behavioral replacement at zero dep cost. Doctrinal bonus: generator scripts now have a node-stdlib-only footprint, matching `generate-version.ts`'s shape. No upward-walk module-resolution surprises possible. Aligns with task #209 ("npm start IS the headless Rust binary, period") — fewer Node deps in the build path is unambiguously good. Verified locally: cd src && npx tsx ../tools/generator/generate-config.ts -> "shared/config.ts unchanged" (idempotent on re-run) -> HTTP_PORT/WS_PORT defaults pick up correctly -> ACTIVE_EXAMPLE resolved from main package.json Net diff: -1 import + 6 lines removed, +33 lines added (parseEnvText + doc block explaining WHY this exists). No behavior change on the happy path. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
joelteply
added a commit
that referenced
this pull request
Jul 20, 2026
…s (kills webdev cross-task contamination) A from-scratch build task (ui_checks present, no setup/dod/solution that establishes or depends on prior repo state) is graded by observing the artifact the persona just wrote into the pinned workspace_root. When the previous task's files still sat there, this task's grade observed a stale/foreign artifact — the exact contamination that scored webdev 0/6 while she built a correct page each time. Harness noise, not a capability miss. run_pass now wipes the pinned root's CONTENTS (not the dir — her hands are rooted at it, via clean_dir_contents) before each from-scratch build task, so every task grades EXACTLY the artifact it produced. Only from-scratch build tasks are cleaned; setup/dod/solution tasks OWN their state and are never touched. No pinned root (hands on core cwd) → no-op. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo
joelteply
added a commit
that referenced
this pull request
Aug 3, 2026
…kspace, never the shared checkout (#312) (#2134) Root cause of the exam↔live contamination that degraded the whole resident room: with no pinned workspace_root, the eval fork's hands rooted at the CORE CWD (the real repo). Fixture writes and #209 per-task wipes landed in the shared world every persona perceives, and gym debris (conway_game_of_life, work-*, bakery fixtures) accumulated as the personas' "own" projects — their workspace-map grounding then faithfully described a polluted world, which read as corrupted RAG. The MIND side was already isolated (fork_detached admission, NoopSink persistence, volatile-tier exclusion); the WORLD side was the hole. Fix: when a tool-bearing exam has no explicit workspace_root, provision a per-run CoW clone of the shared checkout under the system temp dir (APFS clonefile / reflink; plain copy where the FS lacks CoW — same platform split as citizen-layer provisioning). Repo-nav exams still see the real tree; writes and wipes land in the disposable copy; an RAII Drop removes it on every return path. Provisioning failure fails LOUD and refuses to run — no silent fallback to the shared checkout. Explicit workspace_root pins (SWE-bench checkouts) still win unchanged. Validated: cargo check + cognition::eval tests green (metal,accelerate). Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo Co-authored-by: Claude Fable 5 <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
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
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)9f26565Update actions checkout to use node 24 (#2226)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)