Skip to content

bump zombienet-sdk version#9506

Closed
pepoviola wants to merge 17 commits intomasterfrom
jv-bump-zombienet
Closed

bump zombienet-sdk version#9506
pepoviola wants to merge 17 commits intomasterfrom
jv-bump-zombienet

Conversation

@pepoviola
Copy link
Copy Markdown
Contributor

Update zombienet-sdk to latest version.
Thx!

cc: @AndreiEres

@pepoviola pepoviola added R0-no-crate-publish-required The change does not require any crates to be re-published. T10-tests This PR/Issue is related to tests. T18-zombienet_tests Trigger zombienet CI tests. labels Aug 18, 2025
@paritytech-workflow-stopper
Copy link
Copy Markdown

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/17087038931
Failed job name: test-linux-stable

Copy link
Copy Markdown
Contributor

@lrubasze lrubasze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AndreiEres
Copy link
Copy Markdown
Contributor

test-linux-stable failed. I suppose the compilation errors after the bump should be fixed.

@pepoviola
Copy link
Copy Markdown
Contributor Author

  --> /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/subxt-0.38.1/src/lib.rs:19:1
   |
19 | compile_error!("subxt: exactly one of the 'web' and 'native' features should be used.");
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    Rustc finished with error: exit status 1
error: could not compile `subxt` (lib) due to 1 previous error

Looks like maybe we need to add one of this features

@AndreiEres
Copy link
Copy Markdown
Contributor

Looks like maybe we need to add one of this features

I think you should use native.

@pepoviola
Copy link
Copy Markdown
Contributor Author

Looks like maybe we need to add one of this features

I think you should use native.

wait, something is weird, since the latest version of subxt is 0.43 (that the one I updated in zombienet-sdk). Maybe I miss updated in other place. Let me check.

Thx!

pepoviola and others added 14 commits August 26, 2025 12:02
Fixes the benchmarking code of `pallet_session` such that it works with
any `KeyDeposit`.

Reported by @bkontur in
polkadot-fellows/runtimes#855

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
This PR enables `TopicIdTracker` to support multiple flows.

Continues on  #9313
Closes #8676 to fix #8326

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Andrii <ndk@parity.io>
This PR fixes build-binary flow, that is used to build a binary for the
testing purposes from any branch. The issue was that there were too many
input args for the build script.
# Description

Adds a few crate bumps associated to PRs which missed to bump them, and
updates parity-publish version across the board to 0.10.6 (to support
rustc 1.88).

Additionally, makes it so that parity-publish-check-compile runs first
on all unreleased prdocs to bump associated crates, and only after
moving those to an `unreleased` directory, runs on the current PR's
prdoc. This is so that we first create a "local release" based on the
unreleased prdocs, and then we follow with a "patch" release based on
the previous local release, considering only the prdoc pushed with the
current PR. If the workflow fails at the end it means current PR missed
certain bumps. If we don't do the plan/apply twice we risk to miss bumps
due to all prdocs being considered (current PR's prdoc + unreleased
ones) when running parity-publish plan/apply, which might result in a
set of crate bumps which are sufficient, but once some unreleased prdocs
will be moved to a stable prodoc directory, because they will be part of
a stable release, then the ones left will not be enough from a bump
perspective (e.g. like it happened in #9320). That's why it is important
to check every PR that adds a prdoc whether it is self-sufficient from a
crates bumping perspective.

If no prdoc is provided, the parity-publish does not need to be taken
into consideration, but it should also pass nonetheless.

## Integration

N/A

## Review Notes

There seems to a be a corner case parity-publish can not easily catch.
All bumps below are a manifestation of it. More details below:

* #8714 - a major bump is necessary for `sp-wasm-interface` - context
here:
#8714 (comment)
* `sp-keystore` was bumped during 2506 in #6010 , and the relevant prdoc
got moved to stable2506 dir in #9320. This moved prdoc coexisted
alongside other unreleased prdocs, and covered a needed patch bump for
`sp-keystore`, that is not easily visible, and also required for crates
publishing IIUC:
1. `sp-io` is major bumped because its direct dependency,
`sp-state-machine`, was major bumped.
2. `sp-io` has a direct dependency on `sp-core` (minor bumped), and
`sp-keystore` (not touched, not bumped by now)
3. `sp-io` fails to compile because it pulls same types from different
`sp-core` versions (it implements `Keystore` trait from `sp-keystore`
with methods signatures referencing types from `sp-core 38.0.0` by using
the `sp-core 0.38.1` - unreleased yet - types, which confuses rustc).
* `sp-rpc` needs a bump too due to pulling `sp-core 38.0.0`, like
`sp-keystore`, and it is an indirect dependency of `polkadot-cli`, which
has also a direct dependency on unreleased `sp-core 38.1.0`, so again,
if we don't bump `sp-rpc` (historically it has been bumped only with
major, but I think we can go with patch on this one), `polkadot-cli`
can't compile.
* `sc-storage-monitor` is in a similar situation as
`sp-rpc`/`sp-keystore` - `polkadot-cli` depends on `sc-storage-monitor`
(which is not bumped, and has a dependency on `sp-core 38.0.0`), but it
also depends on `sp-core 38.1.0`. And yet again, something is used in
`polkadot-cli` from the two different `sp-core` versions, which confuses
rustc.

---------

Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Alexander Samusev <41779041+alvicsam@users.noreply.github.com>
- Added 2 jobs to `Release - Build node release candidate` CI workflow
for linux/mac subkey binaries
- Added 2 jobs to `RC Build` CI workflow to upload linux/mac `subkey`
artifacts to S3
- updated `release_lib.sh` to reflect new S3 artifacts

CLOSES: #9465

---------

Co-authored-by: EgorPopelyaev <egor@parity.io>
# Description

`publish-check-compile` workflows fails if the PR has no prdoc. Add a
few checks everytime we assume a prdoc exists.

## Integration

N/A

## Review Notes

N/A

Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
Follow-up to #8877 and
audits: Make it such that invulnerable accounts cannot be ejected from
the election signed queue altogether.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Dónal Murray <donal.murray@parity.io>
This PR replaces `log` with `tracing` instrumentation on
`pallet-bridge-relayers` by providing structured logging.

Partially addresses #9211
This PR backport regular version bumps and prdocs reordering from the
stable2506 branch back to master
…#9201)

# Description

- log::info! the error of accessing `GetParachainInfo::parachain_id()`
runtime api if any, before reading the `para_id` from the chain
specification (relevant for debugging).
- removes comments/deprecation notices throughout the code that
introduce `para-id` flag removal (from chain-spec-builder and support
for parsing it from chain specifications)

Closes #9217 

## Integration

N/A

## Review Notes

N/A

---------

Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Sebastian Kunert <mail@skunert.dev>
Co-authored-by: Andrei Sandu <54316454+sandreim@users.noreply.github.com>
- Update some serde encoding for eth-rpc to match serialization behavior
of Geth
- Add support for serializing / deserializing EIP7702 tx types
- Disable transaction type we don't support yet in
try_ino_unchecked_extrinsics

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR:
- improves `take_first_concatenated_xcm()` avoiding the XCM re-encoding
- makes the benchmarks for `take_first_concatenated_xcm()` more
granular, accounting for the number of bytes of the message

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Society pallet supports non-consecutive block provider

Society pallet correctly handles situations where `on_initialize` is
invoked with block numbers that:
- increase but are not strictly consecutive (e.g., jump from 5 → 10), or
- are repeated (e.g., multiple blocks are built at the same Relay Chain
parent block, all reporting the same BlockNumberProvider value).

This situation may occur when the BlockNumberProvider is not local - for
example, on a parachain using the Relay Chain block number provider.

---------

Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
@pepoviola pepoviola requested review from a team and acatangiu as code owners August 26, 2025 10:04
@paritytech-review-bot paritytech-review-bot bot requested a review from a team August 26, 2025 10:05
@pepoviola pepoviola closed this Aug 28, 2025
bkchr added a commit that referenced this pull request Sep 2, 2025
Replace #9506

---------

Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Bastian Köcher <info@kchr.de>
lrubasze pushed a commit that referenced this pull request Sep 17, 2025
Replace #9506

---------

Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Bastian Köcher <info@kchr.de>
alvicsam pushed a commit that referenced this pull request Oct 17, 2025
Replace #9506

---------

Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Bastian Köcher <info@kchr.de>
pgherveou pushed a commit that referenced this pull request Dec 5, 2025
Replace #9506

---------

Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Bastian Köcher <info@kchr.de>
@pepoviola pepoviola deleted the jv-bump-zombienet branch January 8, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R0-no-crate-publish-required The change does not require any crates to be re-published. T10-tests This PR/Issue is related to tests. T18-zombienet_tests Trigger zombienet CI tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.