Bump the npm_and_yarn group across 1 directories with 1 update#5
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
Bumps the npm_and_yarn group with 1 update in the /contracts directory: [axios](https://github.com/axios/axios). Updates `axios` from 1.6.3 to 1.6.4 - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.6.3...v1.6.4) --- updated-dependencies: - dependency-name: axios dependency-type: direct:production dependency-group: npm_and_yarn-security-group ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
Looks like axios is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/contracts/npm_and_yarn-security-group-6b11251bc2
branch
curryxbo
pushed a commit
that referenced
this pull request
May 8, 2026
…C / mutex skeletons
Adds non-runtime skeletons for the four pieces of SPEC-005 work that are
gated on pending blocking decisions (tech-design §8). All four files are
self-contained and compile, but none are wired into the main derivation
loop yet — switching them on requires the corresponding §8 decisions to
land. Each TODO is annotated with the specific blocking item.
What this commit adds:
- node/derivation/verify_path_b.go (SPEC-005 §3.3 path B):
Eligibility check (last_block ≤ safe_head + locally present) and
trigger condition matching tech-design §3.2.2. Stub returns
errPathBUnavailable; the actual blob-rebuild encoder is left as a
TODO pending confirmation that we should reuse tx-submitter helpers
rather than duplicate them (open question §8 #3).
- node/derivation/verify.go::rollbackLocalChain (SPEC-005 §5.2):
Replaces the previous stub message with the formal 8-step atomic
ordering, plus a checkRollbackBoundary helper that enforces the
finalized_head boundary (SPEC-005 §3.6). The actual SetHead call is
still TODO and depends on §8 #4 (go-ethereum hash-matched SetHead).
- node/derivation/sequencer_mutex.go (SPEC-005 §3.6 / §4):
SequencerMutex primitive (RWMutex-based for now) with public
Acquire/Release Production / Rollback methods. Granularity (global
stop-the-world vs interval lock) intentionally hidden behind the
method API so §8 #5 can switch implementation without churning
callers.
- node/derivation/admin_rpc.go (SPEC-005 §5.1):
AdminAPI.SetL2Head(number, hash) skeleton. Hash-matched per
tech-design §3.3 and rejects targets below finalized_head before
delegating to the rollback executor. Authentication wiring blocked
on §8 #2.
No call sites are modified; runtime behaviour is unchanged. P3 unblocks
parallel work on §8 decisions: while operators decide on auth /
mutex granularity / SetHead semantics, downstream developers can build
tests against these signatures.
Refs: morph-l2/morph-specs SPEC-005 §3.3 / §3.6 / §4 / §5 / §8
Co-authored-by: Cursor <cursoragent@cursor.com>
6 tasks
curryxbo
pushed a commit
that referenced
this pull request
May 9, 2026
…ed head anchors Per morph-specs SPEC-005 §6.2 task table: #5 Drive derivation main loop on L1 safe; reorg detection unconditional #6 Persist safe_head anchor after each verified batch (+ metric) #6b finalized_head tracker advances at the tail of every iteration Changes: - node/derivation/config.go Default `Confirmations` flips from FinalizedBlockNumber to SafeBlockNumber, matching SPEC-005 §3.1 step 1. Operators may still override via `--derivation.confirmations`. - node/derivation/derivation.go - Step 1: drop the `confirmations != Finalized` guard around detectReorg — reorg detection now runs every loop on the safe segment, per SPEC-005 §3.2. - After verifyBatchRoots success, write a HeadAnchor (L2 last block + L1 commit block) as the new safe_head and update SafeHeadL2Number metric. - End of loop: invoke advanceFinalizedHead from the new finalized tracker. - node/derivation/finalized_tracker.go (new) advanceFinalizedHead implements SPEC-005 §3.1 step 4. Two paths: cheap path: safe_head.L1Number ≤ L1 finalized → ratchet to safe_head. steady-state: walk commit-batch logs in (currentFinalized, L1 finalized], decode-light the latest one, anchor finalized_head at its L2 last block. Calldata-only — never fetches blob data. Monotonicity is enforced; any regression attempt halts the node. - node/derivation/dual_channel.go Update header comment now that the main loop and finalized tracker are wired into both cursors. Out of scope (per spec §6.2 / §8 and per project decision to leave full rollback for the rollback-executor PR): - L1 anchor window depth tuning (#7 / §8 #1) - Path B implementation (#10) — skeleton stays - Rollback executor (#12) — skeleton stays in verify.go - Sequencer mutex wiring (#11) — skeleton stays - Admin RPC auth (#13 / §8 #2) — skeleton stays
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 the npm_and_yarn group with 1 update in the /contracts directory: axios.
Updates
axiosfrom 1.6.3 to 1.6.4Release notes
Sourced from axios's releases.
Changelog
Sourced from axios's changelog.
Commits
8790b8echore(release): v1.6.4 (#6173)0ad520dchore(ci): fix notify action; (#6172)3c0c11cfix(security): fixed formToJSON prototype pollution vulnerability; (#6167)75af1cdfix(security): fixed security vulnerability in follow-redirects (#6163)90864b3docs: update logos1542719docs: updated headline sponsorsDependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.