Skip to content

[pull] main from agglayer:main#129

Merged
pull[bot] merged 2 commits into
Jokacar10:mainfrom
agglayer:main
Jun 9, 2026
Merged

[pull] main from agglayer:main#129
pull[bot] merged 2 commits into
Jokacar10:mainfrom
agglayer:main

Conversation

@pull

@pull pull Bot commented Jun 9, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

Freyskeyd added 2 commits June 9, 2026 10:04
#1567)

Removes the direct SP1 SDK dependencies from agglayer-types so it
reaches
SP1 only through the agglayer-sp1 facade (issue #1524, epic #1541).

- Drop sp1-sdk, sp1-sdk-v5, sp1-core-machine and sp1-prover from
  agglayer-types; sp1-core-machine and sp1-prover were already unused.
- Move the test-only mock-proof builder
  dummy_sp1_stark_proof_with_version (and its private serialize helper)
  into agglayer-sp1::testutils, and re-export it from
  agglayer_types::testutils so every consumer (agglayer-storage,
  agglayer-grpc-api, agglayer-grpc-types, internal tests) is unchanged.
- Public API of agglayer-types is unchanged. The v5 mock path is
  preserved; full v5 SDK removal is tracked separately in #1511.

Verification: cargo check --workspace --tests --all-features; workspace
clippy -D warnings; nightly fmt --check; cargo nextest for agglayer-sp1
and agglayer-types (28 passed); consumer tests (agglayer-storage types
121, grpc-types compat 19, grpc-api cert-submission 1).

Closes #1524
)

The node startup log printed `VERGEN_IDEMPOTENT_OUTPUT` instead of a
version because the Docker build never receives a `.git` directory, so
vergen cannot derive the git describe/timestamp at compile time.

Resolve the version at compile time from `AGGLAYER_BUILD_DESCRIBE` and
`AGGLAYER_BUILD_TIMESTAMP` when set, falling back to vergen's
git-derived values. Local `cargo build` keeps auto-versioning from
`.git`; Docker and CI builds pass the values explicitly.

- main.rs: prefer the override env vars, fall back to vergen
- build.rs: rerun the build script when the override vars change
- Dockerfile: declare ARG/ENV before `cargo build`, after chef cook so
  the dependency cache is preserved
- docker-build.yml / release.yml: fetch full history and tags, compute
  `git describe --tags --always --dirty` and the commit timestamp, and
  pass them as build-args

A build without the override degrades to vergen's previous behavior
instead of breaking.
@pull pull Bot locked and limited conversation to collaborators Jun 9, 2026
@pull pull Bot added the ⤵️ pull label Jun 9, 2026
@pull pull Bot merged commit 27b2025 into Jokacar10:main Jun 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant