Bump actions/setup-node from 4 to 6 - #1
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
dependabot
Bot
added
dependencies
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/setup-node-6
branch
from
June 9, 2026 07:51
18e2769 to
604d641
Compare
Contributor
Loop Readiness AuditScore: 100/100 (L3) Strong loop readiness — good candidate for L3 with explicit gates. No suggestions — looking good. Posted by |
Contributor
Author
|
Looks like actions/setup-node is up-to-date now, so this is no longer needed. |
50thycal
referenced
this pull request
in 50thycal/loop-engineering
Jun 28, 2026
Adds campaign mode (--search) with the two structural guards that make an auto-search loop safe to turn on — the fixes for self-deception when you are less in the loop: #1 Enforced trial counting (engine/search.py + ledger.py) Every candidate the grid evaluates ticks a counter; it is persisted in research-ledger.json and accumulates ACROSS cycles, then feeds the deflated Sharpe gate. You cannot search 1,000 configs and claim n_trials=1 — the loop counts for you, permanently. #2 Three-way split + write-once lockbox (engine/split.py + ledger.py + verifier.py) Data splits train/validation/lockbox. Search optimizes on train, ranks on validation; the lockbox is opened exactly once, on the winner only. The ledger fingerprints the lockbox and BLOCKS any re-open — re-peeking is self-deception, so the loop refuses. Demonstration on no-edge synthetic data: search finds a winner with validation Sharpe 6.27 (overfit), lockbox opens once and shows Sharpe -9.22 -> REJECT; a second cycle on the same data is BLOCKED; cumulative trials rise across cycles so the deflated bar keeps climbing. The search will always find a beautiful in-sample winner; the lockbox is what stops you believing it. Tests: 14/14 pass (added split, ledger accumulation, write-once, enforced counter, and overfit-winner-rejection). Repo validate gates still pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UcE4n3gQdVXJtD2z3mBrZX
50thycal
referenced
this pull request
in 50thycal/loop-engineering
Jun 28, 2026
… + forward quarantine (cobusgreyling#5) cobusgreyling#4 --trial-budget N: the loop halts searching once cumulative trials reach N. An autonomous loop that searches forever turns the whole dataset into in-sample data; the budget is the alpha-spending cap that forces a stop. Checked before each run (a run may overshoot); once spent, further searches halt and point to forward-testing or new data. engine/ledger.py budget_exhausted(). cobusgreyling#5 --forward-test: carve the newest slice into a quarantine window the search, walk-forward, and lockbox never touch. Research on the earlier window, then forward-test the survivor on the held-out tail. Forward performance gates capital, not the backtest. engine/quarantine.py. Approval requires research AND forward to pass. Each forward window is spent after --max-forward-evals tests (the lockbox lesson, applied to forward data: testing 100 strategies on one tail just relocates the multiple-testing problem). Real BTC demonstration (vol-targeted breakout, 0.40 default): research REJECTs (aggregate drawdown), but the forward out-of-time window actually PASSes cleanly (Sharpe 1.38, +94%, 18% DD on unseen data) — yet the strategy is NOT approved, because approval needs both gates. No single lucky result is sufficient. All five hardening steps (#1-cobusgreyling#5) now implemented. Tests 23/23, repo gates pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UcE4n3gQdVXJtD2z3mBrZX
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/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
48b55a0Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)ab72c7eUpgrade@actionsdependencies (#1525)53b8394Bump minimatch from 3.1.2 to 3.1.5 (#1498)54045abScope test lockfiles by package manager and update cache tests (#1495)c882bffReplace uuid with crypto.randomUUID() (#1378)774c1d6feat(node-version-file): support parsingdevEnginesfield (#1283)efcb663fix: remove hardcoded bearer (#1467)d02c89dFix npm audit issues (#1491)6044e13Docs: bump actions/checkout from v5 to v6 (#1468)8e49463Fix README typo (#1226)