Repository navigation
Bump fast-uri from 3.1.3 to 3.1.8 in /nitro-reth/docs - #4753
Open
dependabot[bot] wants to merge 92 commits into
Open
dependabot[bot] wants to merge 92 commits into
dependabot[bot] wants to merge 92 commits into
Conversation
CODEBUILD_CLONE_REF gives CodeBuild a clone checked out at the source action's configured BranchName, not at the revision the execution resolved, so a tag or commit on any other branch silently builds master's tip. Tag v3.11.x-private-patches-5 (commit c72bfe58) built 25bf717, reported Succeeded and shipped dev-25bf717; the expected image was never built. The "dev" tag is the same cause: HEAD was master's tip, so no v* tag pointed at it. Check out the resolved revision before anything reads git. SOURCE_REF lets an operator name a tag or commit when starting a release; "auto", including when the pipeline does not set it, uses the resolved revision.
CODEBUILD_CLONE_REF gives CodeBuild a clone checked out at the source action's configured BranchName, not at the revision the execution resolved, so a tag or commit on any other branch silently builds master's tip. Tag v3.11.x-private-patches-5 (commit c72bfe58) built 25bf717, reported Succeeded and shipped dev-25bf717; the expected image was never built. The "dev" tag is the same cause: HEAD was master's tip, so no v* tag pointed at it. The clone is complete, so the revision is already present locally and needs no fetch. Re-fetching is not an option anyway: CodeBuild clones with credentials it does not leave behind, so any later call against origin dies with "could not read Username for codestar-connections". Resolve against the local object store instead and fail with the available refs listed if it is missing. SOURCE_REF lets an operator name a tag or commit when starting a release; "auto", including when the pipeline does not set it, uses the resolved revision. Verified in production: execution beb8a5bd moved HEAD from 25bf717 to c72bfe58 and built v3.11.x-private-patches-5-c72bfe5.
Move TestHistoricalBlockHash into the v2 blocks package and delete the v1 test. Declares MinArbOS(40): EIP-2935 history storage is seeded at the ArbOS 40 upgrade, so on an older chain the address holds no code and every call returns empty. v1 could not express this and relied on the dev chain default (59) never moving. Runs L2-only where v1 built an L1. Nothing under test is parent-chain derived; the scenario only produces blocks and reads them back through the history storage contract. Fixes NIT-5556
…czyk/nit-5519-runner-modes # Conflicts: # crates/sp1/replay-runner/main.rs
…l-block-hash-scenario-to-systests-v2 system tests v2: migrate historical block hash scenario
Co-authored-by: joshuacolvin0 <32654531+joshuacolvin0@users.noreply.github.com>
fix(build-pipeline): check out the revision the pipeline resolved
The CodeBuild projects run an inline copy of this buildspec, taken
before the nitroversion refactor renamed the Docker build args from
"version" to tag/branch/commit. Docker only warns about an undeclared
build arg, so v3.12.0-rc.1 shipped as "local+unknown-20260828T193632Z"
with a correct image tag and a green build.
Check the first image built reports both the tag (or branch) and the
commit the pipeline selected. Asserting the commit alone would miss a
rename of tag, which is the worse half: an empty tag leaves
IsSemverTagged false, so CheckVersionBounds and the version alerter
stop enforcing while the binary still names the right commit.
Also drop the ${BUILD_ARGS:-} fallback and export the variable instead.
That is hardening rather than part of the fix -- the incident had a
populated BUILD_ARGS carrying stale arg names -- but it removes the one
value the build phase reads without the producer exporting it.
The comment above the token re-mint claimed a staleness that does not
happen: v3.12.0-rc.1 ran 20:27:30 to 20:50:04, so the token was minutes
old, not expired. Removed rather than replaced with another guess.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
buildspec.yml has built and pushed the per-arch rust-validator images since 30345ca, but the manifest job never aggregated them, so $IMAGE_TAG-rust-validator resolved to nothing while its -amd64 and -arm64 tags existed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A read-only open with the freezer attached needs every chain freezer table on disk, so after the bals table was added upstream the probe failed on every pre-existing store and the node read it as absent. The probe now skips the freezer; the chain config is read below it from the read-write handle, which has the ancients that block 0 needs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fix ci flakyness around BlockValidator shutdown on execution RPC
…r-modes SP1 replay-runner execution modes: fast, simulate, and prove
Don't attach the freezer to the l2chaindata existence probe
…rait arb-stylus adopts arbutil's `EvmApi` trait (dedup 2/n)
…tylus-cut The Stylus compile seam: `arb-stylus` builds for wasm32
…anarios system tests v2: Transfer base scenarios
Make buildspec more resilient
nitro-reth links the prebuilt brotli libs; common CI setup action
(cherry picked from commit db99e32746932215a17aec3bb055e7375a51e343)
Bump go-ethereum to release cancelled eth_getLogs searches (backport #862)
Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.3 to 3.1.8. - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.3...v3.1.8) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.8 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
A newer version of fast-uri exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
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 fast-uri from 3.1.3 to 3.1.8.
Release notes
Sourced from fast-uri's releases.
Commits
ead3ab7Bumped v3.1.8c88b59efix: normalize decoded reg-name case412e40aBumped v3.1.79f4c943fix: backport port and IP-literal validation to v3.x (#216)1eb3ce4fix: treat unterminated bracket hosts as reg-names again (#214)6f970b2Bumped v3.1.6d941579fix: never run IDN canonicalization on bracketed IP literalsc0f0279test: adapt decoded-scheme handler assertion to 3.x (no mailto scheme)37f3417Merge commit from fork607bfbeMerge commit from forkDependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.