Skip to content

fix(deps): update rust crate solana-metrics to v2.3.13 - #13

Open
p2p-renovate[bot] wants to merge 1 commit into
masterfrom
renovate/solana-metrics-2.x
Open

fix(deps): update rust crate solana-metrics to v2.3.13#13
p2p-renovate[bot] wants to merge 1 commit into
masterfrom
renovate/solana-metrics-2.x

Conversation

@p2p-renovate

@p2p-renovate p2p-renovate Bot commented Jul 22, 2026

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
solana-metrics (source) dependencies minor =2.1 → =2.3.13

Release Notes

anza-xyz/agave (solana-metrics)

v2.3.13

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier. If you are still using Ubuntu 20.04, you will need to build the binaries from source.

⚠️ ATTENTION REQUIRED: as of Agave v3.0.0 Anza will no longer publish the agave-validator binary. Operators will need to build agave from source following these instructions: https://docs.anza.xyz/cli/install#build-from-source

What's Changed

Full Changelog: anza-xyz/agave@v2.3.12...v2.3.13

v2.3.12

Compare Source

🚧

v2.3.11

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier. If you are still using Ubuntu 20.04, you will need to build the binaries from source.

⚠️ ATTENTION REQUIRED: as of Agave v3.0.0 Anza will no longer publish the agave-validator binary. Operators will need to build agave from source following these instructions: https://docs.anza.xyz/cli/install#build-from-source

What's Changed

Full Changelog: anza-xyz/agave@v2.3.10...v2.3.11

v2.3.10

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier. If you are still using Ubuntu 20.04, you will need to build the binaries from source.

⚠️ ATTENTION REQUIRED: as of Agave v3.0.0 Anza will no longer publish the agave-validator binary. Operators will need to build agave from source following these instructions: https://docs.anza.xyz/cli/install#build-from-source

What's Changed

Full Changelog: anza-xyz/agave@v2.3.9...v2.3.10

v2.3.9

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier. If you are still using Ubuntu 20.04, you will need to build the binaries from source.

⚠️ ATTENTION REQUIRED: as of Agave v3.0.0 Anza will no longer publish the agave-validator binary. Operators will need to build agave from source following these instructions: https://docs.anza.xyz/cli/install#build-from-source

What's Changed

Full Changelog: anza-xyz/agave@v2.3.8...v2.3.9

v2.3.8

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.7...v2.3.8

v2.3.7

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.6...v2.3.7

v2.3.6

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.5...v2.3.6

v2.3.5

Compare Source

This is a Testnet release. It is also recommended for Devnet.
It is also recommended for up to 25% of Mainnet Beta stake.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.4...v2.3.5

v2.3.4

Compare Source

This is a Testnet release. It is also recommended for Devnet.

It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.3...v2.3.4

v2.3.3

Compare Source

This is a Testnet release. It is also recommended for Devnet.

It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.2...v2.3.3

v2.3.2

Compare Source

This is a Testnet release. It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.1...v2.3.2

v2.3.1

Compare Source

This is a Testnet release. It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.3.0...v2.3.1

v2.3.0

Compare Source

Validator
Breaking
  • ABI of TimedTracedEvent changed, since PacketBatch became an enum, which carries different packet batch types. (#​5646)
Changes
  • Account notifications for Geyser are no longer deduplicated when restoring from a snapshot.
  • Add --no-snapshots to disable generating snapshots.
  • --block-production-method central-scheduler-greedy is now the default.
  • The default full snapshot interval is now 50,000 slots.
  • Graceful exit (via agave-validtor exit) is required in order to boot from local state. Refer to the help of --use-snapshot-archives-at-startup for more information about booting from local state.
Deprecations
  • Using --snapshot-interval-slots 0 to disable generating snapshots is now deprecated.
  • Using blockstore-processor for --block-verification-method is now deprecated.
Platform Tools SDK
Changes
  • cargo-build-sbf and cargo-test-sbf now accept v0, v1, v2 and v3 for the --arch argument. These parameters specify the SBPF version to build for.
  • SBFPv1 and SBPFv2 are also available for Anza's C compiler toolchain.
  • SBPFv3 will be only available for the Rust toolchain. The C toolchain will no longer be supported for SBPFv3 onwards.
  • cargo-build-sbf now supports the --optimize-size argument, which reduces program size, potentially at the cost of increased CU usage.
Breaking
  • Although the solana rust toolchain still supports the sbf-solana-solana target, the new cargo-build-sbf version target defaults to sbpf-solana-solana. The generated programs will be available on target/deploy and target/sbpf-solana-solana/release.
  • If the sbf-solana-solana target folder is still necessary, use cargo +solana build --triple sbf-solana-solana --release.
  • The target triple changes as well for the new SBPF versions. Triples will be sbpfv1-solana-solana for version v1, sbpfv2-solana-solana for v2, and sbpfv3-solana-solana for v3. Generated programs are available on both the target/deploy folder and the target/<triple>/release folder. The binary in target/deploy has smaller size, since we strip unnecessary sections from the one available in target/<triple>/release.
  • cargo-build-sbf no longer automatically enables the program feature to the solana-sdk dependency. This feature allowed solana-sdk to work in on-chain programs. Users must enable the program feature explicitly or use solana-program instead. This new behavior only breaks programs using solana-sdk v1.3 and earlier.
CLI
Changes
  • withdraw-stake now accepts the AVAILABLE keyword for the amount, allowing withdrawal of unstaked lamports (#​4483)
  • solana-test-validator will now bind to localhost (127.0.0.1) by default rather than all interfaces to improve security. Provide --bind-address 0.0.0.0 to bind to all interfaces to restore the previous default behavior.
RPC
Changes
  • simulateTransaction now includes loadedAccountsDataSize in its result. loadedAccountsDataSize is the total number of bytes loaded for all accounts in the simulated transaction.

v2.2.20

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.19...v2.2.20

v2.2.19

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.18...v2.2.19

v2.2.18

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.17...v2.2.18

v2.2.17

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.16...v2.2.17

v2.2.16

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

v2.2.15

Compare Source

This is a stable release suitable for use on Mainnet Beta.

As of May 2025, Ubuntu 20.04 has reached its End of Life (EOL) for standard support. Due to this, new binaries are now built using Ubuntu 22.04, and are not compatible with Ubuntu 20.04 or earlier.

⚠️ If you are still using Ubuntu 20.04, you will need to build the binaries from source.

We recommend upgrading to Ubuntu 22.04 or later for continued compatibility and support.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.14...v2.2.15

v2.2.14

Compare Source

This is a Testnet release. It is also recommended for Devnet.

This release is recommended for mainnet-beta for operators who:

  • build their own bins, and
  • don't build on Ubuntu 20.04

What's Changed

Full Changelog: anza-xyz/agave@v2.2.13...v2.2.14

v2.2.13

Compare Source

This is a Testnet release. It is also recommended for Devnet

What's Changed

Full Changelog: anza-xyz/agave@v2.2.12...v2.2.13

v2.2.12

Compare Source

This is a Testnet release. It is also recommended for Devnet, and up to 25% of Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.11...v2.2.12

v2.2.11

Compare Source

This is a Testnet release. It is also recommended for Devnet, and up to 10% of Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.10...v2.2.11

v2.2.10

Compare Source

🚧

v2.2.9

Compare Source

🚧

v2.2.8

Compare Source

🚧

v2.2.7

Compare Source

This is a Testnet release. It is also recommended for Devnet, and up to 10% of Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.6...v2.2.7

v2.2.6

Compare Source

This is a Testnet release. It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.5...v2.2.6

v2.2.5

Compare Source

v2.2.4

Compare Source

This is a Testnet release. It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.3...v2.2.4

v2.2.3

Compare Source

This is a Testnet release. It is not recommended Mainnet Beta.

What's Changed

Full Changelog: anza-xyz/agave@v2.2.2...v2.2.3

v2.2.2

Compare Source

This is a Testnet release. It is not recommended Mainnet Beta.

What's Changed

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@p2p-renovate

p2p-renovate Bot commented Jul 22, 2026

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path searcher_client/Cargo.toml --workspace
    Updating crates.io index
error: failed to select a version for `solana-metrics`.
    ... required by package `solana-perf v2.1.0`
    ... which satisfies dependency `solana-perf = "=2.1"` of package `jito-protos v0.1.0 (/tmp/renovate/repos/github/p2p-org/searcher-examples/jito_protos)`
    ... which satisfies path dependency `jito-protos` (locked to 0.1.0) of package `jito-searcher-cli v0.1.0 (/tmp/renovate/repos/github/p2p-org/searcher-examples/cli)`
versions that meet the requirements `=2.1.0` are: 2.1.0

all possible versions conflict with previously selected packages

  previously selected package `solana-metrics v2.3.13`
    ... which satisfies dependency `solana-metrics = "=2.3.13"` of package `jito-searcher-client v0.1.0 (/tmp/renovate/repos/github/p2p-org/searcher-examples/searcher_client)`
    ... which satisfies path dependency `jito-searcher-client` (locked to 0.1.0) of package `jito-searcher-cli v0.1.0 (/tmp/renovate/repos/github/p2p-org/searcher-examples/cli)`

failed to select a version for `solana-metrics` which could resolve this conflict

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants