Add flow to create old tag (#98)

* [CI/CD] Check semver job improvements (paritytech#10323)

This PR adds couple of improvements to the Check semver job for the
stable branches:
1. The `validate: false` option can be set now not only on the `mojor`
bumps but on the `minor` and `patch` as well, this one is useful when
for the backport cases when a desired bump does not match with the one,
that `parity-publish` semver check has predicted (like
[here](https://github.com/paritytech/polkadot-sdk/actions/runs/19135068993/job/54685184577?pr=10221))
2. Possibility to skip check, when it is really not needed but still
fails (like on the post crates release
[prs](https://github.com/paritytech/polkadot-sdk/actions/runs/18311557391/job/52141285274?pr=9951))

closes: paritytech/release-engineering#274

* Cumulus: fix pre-connect to backers for lonely collators (paritytech#10305)

When running a single collator (most commonly on testnets), the block
builder task is always able to claim a slot, so we're never triggering
the pre-connect mechanism which happens for slots owned by other
authors.
Additionally I fixed some tests.

---------

Signed-off-by: Andrei Sandu <[email protected]>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* frame-system: Only enable special benchmarking code when running in `no_std` (paritytech#10321)

This fixes `cargo test -p cumulus-pallet-parachain-system --features
runtime-benchmarks`

* fix: support `paginationStartKey` parameter for `archive_v1_storage` (paritytech#10329)

Fixes paritytech#10185

This PR is to add support for `paginationStartKey` parameter in
`archive_v1_storage` JSON RPC API for query type: `descendantsValues`
and `descendantsHashes` per [the latest
specs](https://paritytech.github.io/json-rpc-interface-spec/api/archive_v1_storage.html).

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <[email protected]>

* Rename `SlotSchedule` to `TargetBlockRate` (paritytech#10316)

This renames the `SlotSchedule` runtime api to `TargetBlockRate`. It
also changes the signature to only returning the target block rate. As
discussed at the retreat, we don't need the block time returned as part
of this runtime api.

* chore: update zombienet environment vars (paritytech#10293)

# Description
paritytech#9724

---------

Co-authored-by: Javier Viola <[email protected]>

* Skip building on blocks on relay parents in old session (paritytech#9990)

Fixes: paritytech#9977

On our Kusama Canary chain YAP-3392 has the log entry:
```
Collation wasn't advertised because it was built on a relay chain block that is now part of an old session
``` 
[show up 400+ times (2025-10-03 --
2025-10-10)](https://grafana.teleport.parity.io/goto/spoPcDeHR?orgId=1).

# Changes
Changed `offset_relay_parent_find_descendants` to return `None` if the
`relay_best_hash` or any of its ancestors contains an epoch change.

---------

Co-authored-by: Sebastian Kunert <[email protected]>

* ci: ci-unified with resolc 0.5.0 (paritytech#10325)

cc paritytech/devops#4508
cc @athei

* Introduce `ReplayProofSizeProvider`, `RecordingProofProvider` & transactional extensions (paritytech#9930)

The `ProofSizeExt` extension is used to serve the proof size to the
runtime. It uses the proof recorder to request the current proof size.
The `RecordingProofProvider` extension can record the calls to the proof
size function. Later the `ReplayProofSizeProvider` can be used to replay
these recorded proof sizes. So, the proof recorder is not required
anymore.

Extensions are now also hooked into the transactional system. This means
they are called when a new transaction is created and informed when a
transaction is committed or reverted.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* fix P256Verify precompile address (paritytech#10336)

fix paritytech/contract-issues#220

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* parachain-consensus: Do not pin blocks on the relay chain during syncing (paritytech#10333)

We had reports in the past about `polkadot-parachain` consuming a lot of
memory during syncing. I spend some time investigating this again.

This graph shows memory consumption during sync process:
<img width="1256" height="302" alt="image"
src="https://github.com/user-attachments/assets/eec1b510-1aa8-446e-8088-5ff0daab6252"
/>

We see a rise up to 50gb and then release of a lot of memory and node
stabilizes at around 20gb. While I still find that relatively high, I
found that the large reduction in memory towards the end was caused by
finality notifications. I tracked down the culprit to be
`parachain-consensus`. It is doing long-blocking finalization operations
and keeps finality notifications around while doing so.

In this PR I introduce a new task that fetches the included block and
then immediately releases the finality notifications of the relay chain.

Memory is now more bounded at around ~12gb:
<img width="1248" height="308" alt="image"
src="https://github.com/user-attachments/assets/5a8be3bb-02a2-400f-9d0d-87ec298ce09f"
/>

closes paritytech#1662

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Allow DT CI to be manually triggered (paritytech#10337)

# Description

This is a small PR that allows for the differential testing job to be
manually triggered instead of _only_ being triggered by PRs.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* [Release|CI/CD] Use larger runners only for the polkadot-parachain and polkadot-omni-node builds (paritytech#10343)

This PR changes the RC build flow so that the large github runners will
be used only for the `polakdot-parachain` and `polkadot-omni-node`
builds, as other binaries builds run fine on the standard runners and
what helps as well to save some costs and resources.

closes: paritytech/release-engineering#279

* Make tasks local only. (paritytech#10162)

Related to paritytech#9693

In the transaction pool, transaction are identified by the tag they
provide.

For tasks the provided tag is simply the hash for the encoded task.

Nothing in the doc says that implementers should be careful that tasks
are not too many for a single operation. What I mean is if a task is
`migrate_keys(limit)`, with valid first from 1 to 10_000. Then all tasks
`migrate_keys(1)`, `migrate_keys(2)` ... `migrate_keys(10_000)` are
valid and effectively do the same operation: they all migrate part of
the keys.
In this case a malicious person can submit all those tasks at once and
spam the transaction pool with 10_000 transactions.

I see multiple solution:
* (1) we are careful when we implement tasks, we make the doc clear, but
the API is error prone. (in my example above we would implement just
`migrate_keys` and inside the call we would do a basic rate of migration
of 1000 keys in a bulk).
* (2) we have a new value returned that is the provided tag for the
task. Or we use the task index as provided tag.
* (3) we only accept local tasks: <-- implemented in this PR.

maybe (2) is a better API if we want external submission of tasks.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Version bumps and prdocs reordering from stable2509-2 (paritytech#10339)

This PR backports regular version bumps and prdoc reordering from the
release branch back to master

* Fix the `CodeNotFound` issue in PolkaVM tests (paritytech#10298)

# Description

This PR bumps the commit hash of the revive-differential-tests framework
to a version that contains a fix for the `CodeNotFound` issue we've been
seeing with PolkaVM. The framework now uploads the code of all the
contracts prior to running the tests.

When CI runs for this PR we should observe that there's either no more
`CodeNotFound` errors in PolkaVM tests or that it's greatly reduced.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Don't require PR for uploading comment for DT CI (paritytech#10347)

# Description

Small PR that changes the DT CI to not require a PR for uploading the
report to the CI job.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* add flow to create an old tag

---------

Signed-off-by: Andrei Sandu <[email protected]>
Co-authored-by: Andrei Sandu <[email protected]>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Thang X. Vu <[email protected]>
Co-authored-by: DenzelPenzel <[email protected]>
Co-authored-by: Javier Viola <[email protected]>
Co-authored-by: Alexander Cyon <[email protected]>
Co-authored-by: Sebastian Kunert <[email protected]>
Co-authored-by: Alexander Samusev <[email protected]>
Co-authored-by: PG Herveou <[email protected]>
Co-authored-by: Omar <[email protected]>
Co-authored-by: Guillaume Thiolliere <[email protected]>
Co-authored-by: BDevParity <[email protected]>

Author: 14 people

.github/env

@@ -1 +1 @@
-IMAGE="docker.io/paritytech/ci-unified:bullseye-1.88.0-2025-06-27-v202509220255"
+IMAGE="docker.io/paritytech/ci-unified:bullseye-1.88.0-2025-06-27-v202511141243"

.github/scripts/process-differential-tests-report.py

@@ -225,7 +225,9 @@ def main() -> None:
                 if status["status"] != "Failed":
                     continue
 
-                failure_reason: str = status["reason"].replace("\n", " ")
+                failure_reason: str = (
+                    status["reason"].replace("\n", " ").replace("|", " ")
+                )
 
                 note: str = ""
                 modes_where_this_case_succeeded: set[ModeString] = (

.github/workflows/check-semver.yml

@@ -106,23 +106,67 @@ jobs:
 
       - name: Check semver
         if: ${{ github.ref != 'refs/heads/master' }}
+        shell: bash
         env:
           PRDOC_EXTRA_ARGS: ${{ env.PRDOC_EXTRA_ARGS }}
           PR: ${{ env.PR_NUMBER }}
           BASE_BRANCH: ${{ github.event.pull_request.base.ref }}
+          PR_LABELS: ${{ toJson(github.event.pull_request.labels.*.name) }}
         run: |
           if [ -z "$PR" ]; then
             echo "Skipping master/merge queue"
             exit 0
           fi
 
+          # Skip semver check if PR targets stable branch and has R0-no-crate-publish-require label
+          if [[ "$BASE_BRANCH" =~ ^stable[0-9]{4}$ ]]; then
+            if echo "$PR_LABELS" | grep -q "R0-no-crate-publish-require"; then
+              echo "ℹ️ Skipping the SemVer check is not recommended and should only be done in rare cases: PR targets stable branch '$BASE_BRANCH' and has 'R0-no-crate-publish-require' label."
+              exit 0
+            fi
+          fi
+
           export CARGO_TARGET_DIR=target
           export RUSTFLAGS='-A warnings -A missing_docs'
           export SKIP_WASM_BUILD=1
 
-          if ! parity-publish --color always prdoc --since old --validate prdoc/pr_$PR.prdoc $PRDOC_EXTRA_ARGS -v --toolchain $TOOLCHAIN; then
+          prdoc_file="prdoc/pr_$PR.prdoc"
+
+          # Always run parity-publish to check for all issues (mismatches and missing crates)
+          # Capture output to check for specific error types
+          parity_output=$(mktemp)
+          if ! parity-publish --color always prdoc --since old --validate prdoc/pr_$PR.prdoc $PRDOC_EXTRA_ARGS -v --toolchain $TOOLCHAIN 2>&1 | tee "$parity_output"; then
+
+            # Check if there are missing crates (files changed but not listed in prdoc)
+            if grep -q "Files changed but crate not listed in PR Doc" "$parity_output"; then
+              rm -f "$parity_output"
+              cat <<EOF
+
+          👋 Hello developer! The SemVer check found crates with changes that are not listed in the prdoc file.
+
+          It is recommended to add all changed crates to the prdoc.
+
+          Please check the output above and see the following links for more help:
+          - https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/prdoc.md#record-semver-changes
+          - https://forum.polkadot.network/t/psa-polkadot-sdk-to-use-semver
+
+          Otherwise feel free to ask in the Merge Request or in Matrix chat.
+          EOF
+
+              exit 1
+            fi
+
+            rm -f "$parity_output"
+
+            # Check if any crate has validate: false to override semver mismatch failures
+            if grep -q "validate:[[:space:]]*false" "$prdoc_file"; then
+              echo ""
+              echo "ℹ️ Found crates with 'validate: false' in prdoc. Semver validation failure is overridden."
+              echo "⚠️ Please ensure the semver override is justified and documented in the PR description."
+            else
+              # No validate: false found, fail with error message
+              cat <<EOF
 
-            cat <<EOF
           👋 Hello developer! The SemVer information that you declared in the prdoc file did not match what the CI detected.
 
           Please check the output above and see the following links for more help:
@@ -132,7 +176,10 @@ jobs:
           Otherwise feel free to ask in the Merge Request or in Matrix chat.
           EOF
 
-            exit 1
+              exit 1
+            fi
+          else
+            rm -f "$parity_output"
           fi
 
           # Only enforce SemVer restrictions for backports targeting stable branches
@@ -143,7 +190,28 @@ jobs:
 
           echo "🔍 Backport branch detected, checking for disallowed semver changes..."
 
-          prdoc_file="prdoc/pr_$PR.prdoc"
+          # Check for minor/patch bumps with validate: false
+          if grep -qE "bump:[[:space:]]*(minor|patch)" "$prdoc_file"; then
+              minor_patch_temp=$(mktemp)
+              grep -A1 -E "bump:[[:space:]]*(minor|patch)" "$prdoc_file" > "$minor_patch_temp"
+
+              has_validate_false=false
+              while read -r line; do
+                  if [[ "$line" =~ bump:[[:space:]]*(minor|patch) ]]; then
+                      read -r next_line
+                      if [[ "$next_line" =~ validate:[[:space:]]*false ]]; then
+                          has_validate_false=true
+                          break
+                      fi
+                  fi
+              done < "$minor_patch_temp"
+
+              rm -f "$minor_patch_temp"
+
+              if [ "$has_validate_false" = true ]; then
+                  echo "ℹ️ Found minor/patch bumps with validate: false override. Semver validation was skipped for these crates by parity-publish."
+              fi
+          fi
 
           # Check if there are any major bumps
           if ! grep -q "bump:[[:space:]]*major" "$prdoc_file"; then
@@ -155,24 +223,34 @@ jobs:
           temp_file=$(mktemp)
           grep -A1 "bump:[[:space:]]*major" "$prdoc_file" > "$temp_file"
 
-          while read -r line; do
+          error_found=false
+          while IFS= read -r line; do
               if [[ "$line" =~ bump:[[:space:]]*major ]]; then
                   # This is the bump line, read the next line
-                  read -r next_line
-                  if [[ "$next_line" =~ validate:[[:space:]]*false ]]; then
-                      continue  # This major bump is properly validated
+                  if IFS= read -r next_line; then
+                      if [[ "$next_line" =~ validate:[[:space:]]*false ]]; then
+                          continue  # This major bump is properly validated
+                      else
+                          error_found=true
+                          break
+                      fi
                   else
-                      echo "❌ Error: Found major bump without 'validate: false'"
-                      echo "📘 See: https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/prdoc.md#backporting-prs"
-                      echo "🔧 Add 'validate: false' after the major bump in $prdoc_file with justification."
-                      rm -f "$temp_file"
-                      exit 1
+                      # No next line, means no validate: false
+                      error_found=true
+                      break
                   fi
               fi
           done < "$temp_file"
 
           rm -f "$temp_file"
 
+          if [ "$error_found" = true ]; then
+              echo "❌ Error: Found major bump without 'validate: false'"
+              echo "📘 See: https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/prdoc.md#backporting-prs"
+              echo "🔧 Add 'validate: false' after the major bump in $prdoc_file with justification."
+              exit 1
+          fi
+
           # If we reach here, all major bumps have validate: false
           echo "⚠️ Backport contains major bumps, but they are all marked with validate: false."
           echo "✅ Semver override accepted. Please ensure justification is documented in the PR description."

.github/workflows/release-30_publish_release_draft.yml

@@ -179,7 +179,7 @@ jobs:
           GITHUB_TOKEN: ${{ steps.generate_write_token.outputs.token }}
         run: |
           mkdir -p ${{ github.workspace}}/runtimes/
-          gh run download ${{ github.event.inputs.build_run_id }} --dir ${{ github.workspace}}/runtimes
+          gh run download ${{ inputs.build_run_id }} --dir ${{ github.workspace}}/runtimes
           ls -la ${{ github.workspace}}/runtimes
 
       - name: Get runtime info

.github/workflows/release-60_create-old-release-tag.yml

@@ -0,0 +1,63 @@
+name: Release - Create polkadot-vX.YY.Z tag
+# This workflow creates a final release tag in the old format (e.g. polkadot-v1.20.0) for a published release.
+
+on:
+  release:
+    types: published
+
+jobs:
+  create-old-release-tag:
+    runs-on: parity-default
+    environment: release
+    env:
+      PGP_KMS_KEY: ${{ secrets.PGP_KMS_SIGN_COMMITS_KEY }}
+      PGP_KMS_HASH: ${{ secrets.PGP_KMS_HASH }}
+      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+      AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+      AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION }}
+
+    steps:
+      - name: Install pgpkkms
+        run: |
+          # Install pgpkms that is used to sign commits
+          pip install git+https://github.com/paritytech-release/pgpkms.git@6cb1cecce1268412189b77e4b130f4fa248c4151
+
+      - name: Generate content write token for the release automation
+        id: generate_write_token
+        uses: actions/create-github-app-token@67018539274d69449ef7c02e8e71183d1719ab42 # v2.1.4
+        with:
+            app-id: ${{ vars.RELEASE_AUTOMATION_APP_ID }}
+            private-key: ${{ secrets.RELEASE_AUTOMATION_APP_PRIVATE_KEY }}
+            owner: paritytech
+
+      - name: Checkout
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        with:
+          ref: ${{ github.event.release.tag_name }}
+          token: ${{ steps.generate_write_token.outputs.token }}
+
+      - name: Import gpg keys
+        run: |
+          . ./.github/scripts/common/lib.sh
+
+          import_gpg_keys
+
+      - name: Config git
+        run: |
+          git config --global commit.gpgsign true
+          git config --global gpg.program /home/runner/.local/bin/pgpkms-git
+          git config --global user.name "ParityReleases"
+          git config --global user.email "[email protected]"
+          git config --global user.signingKey "D8018FBB3F534D866A45998293C5FB5F6A367B51"
+
+      - name: Create old release tag
+        env:
+          GH_TOKEN: ${{ steps.generate_write_token.outputs.token }}
+        run: |
+          . ./.github/scripts/common/lib.sh
+
+          version=$(get_polkadot_node_version_from_code)
+          echo "Extracted node version: $version"
+
+          git tag -s "polkadot-v${version}" -m "Old release tag polkadot-v${version}"
+          git push origin "polkadot-v${version}"

.github/workflows/release-reusable-rc-build.yml

@@ -42,19 +42,32 @@ jobs:
     # However, env variables don't work for forks: https://github.com/orgs/community/discussions/44322
     # This workaround sets the container image for each job using 'set-image' job output.
     runs-on: ubuntu-latest
+    env:
+      BINARY: ${{ inputs.binary }}
     outputs:
       IMAGE: ${{ steps.set_image.outputs.IMAGE }}
+      RUNNER: ${{ steps.set_image.outputs.RUNNER }}
     steps:
       - name: Checkout
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
 
       - id: set_image
-        run: cat .github/env >> $GITHUB_OUTPUT
+        run: |
+          cat .github/env >> $GITHUB_OUTPUT
+          RUNNER=""
+          if [[ "${BINARY}" =~ "polkadot-parachain" || "${BINARY}" =~ "polkadot-omni-node" ]]; then
+            RUNNER="ubuntu-latest-m"
+            echo "Using ubuntu-latest-m runner"
+          else
+            RUNNER="ubuntu-latest"
+            echo "Using ubuntu-latest runner"
+          fi
+          echo "RUNNER=${RUNNER}" >> $GITHUB_OUTPUT
 
   build-rc:
     if: ${{ inputs.target == 'x86_64-unknown-linux-gnu' }}
     needs: [set-image]
-    runs-on: ubuntu-latest-m
+    runs-on: ${{ needs.set-image.outputs.RUNNER }}
     environment: release
     container:
       image: ${{ needs.set-image.outputs.IMAGE }}

.github/workflows/tests-evm.yml

@@ -7,6 +7,7 @@ on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
   merge_group:
+  workflow_dispatch:
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: true
@@ -50,7 +51,7 @@ jobs:
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
         with:
           repository: paritytech/revive-differential-tests
-          ref: 347dcb4488ac188ef7bddf6e4b4c44b389f881c4
+          ref: a6e4932a08b1ca231e4a02ca6e54e08a53f0e786
           path: revive-differential-tests
           submodules: recursive
       - name: Installing Retester
@@ -84,7 +85,8 @@ jobs:
       # certain cases where the report is too long to post as a Github comment.
       # This happens if the all of the tests are failing and therefore the
       # report exceeds the maximum allowed length of github comments
-      - uses: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4
+      - name: Upload the Report to the CI
+        uses: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4
         with:
           name: report-${{ matrix.platform }}.md
           path: report.md

.github/workflows/tests-misc.yml

@@ -382,7 +382,7 @@ jobs:
       - name: Install resolc
         run: |
           source $HOME/.cargo/env
-          VERSION="0.3.0"
+          VERSION="0.5.0"
           ASSET_URL="https://github.com/paritytech/revive/releases/download/v$VERSION/resolc-universal-apple-darwin"
           echo "Downloading resolc v$VERSION from $ASSET_URL"
           curl -Lsf --show-error -o $HOME/.cargo/bin/resolc "$ASSET_URL"

.github/zombienet-tests/zombienet_cumulus_tests.yml

@@ -1,18 +1,18 @@
 - job-name: "zombienet-cumulus-0001-sync_blocks_from_tip_without_connected_collator"
   test-filter: "zombie_ci::sync_blocks::sync_blocks_from_tip_without_connected_collator"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 - job-name: "zombienet-cumulus-0002-pov_recovery"
   test-filter: "zombie_ci::pov_recovery::pov_recovery"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 - job-name: "zombienet-cumulus-0003-full_node_catching_up"
   test-filter: "zombie_ci::full_node_catching_up::full_node_catching_up"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
 
 - job-name: "zombienet-cumulus-0004-runtime_upgrade"
@@ -30,41 +30,41 @@
 
 - job-name: "zombienet-cumulus-0006-rpc_collator_builds_blocks"
   test-filter: "zombie_ci::rpc_collator_build_blocks::rpc_collator_builds_blocks"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 - job-name: "zombienet-cumulus-0007-full_node_warp_sync"
   test-filter: "zombie_ci::full_node_warp_sync::full_node_warp_sync"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 - job-name: "zombienet-cumulus-0008-elastic_authoring"
   test-filter: "zombie_ci::elastic_scaling::slot_based_authoring::elastic_scaling_slot_based_authoring"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 # Disabled, occasionally fails
 # See https://github.com/paritytech/polkadot-sdk/issues/8986
 - job-name: "zombienet-cumulus-0009-elastic_scaling_pov_recovery"
   test-filter: "zombie_ci::elastic_scaling::pov_recovery::elastic_scaling_pov_recovery"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 # Disabled, occasionally fails.
 # See https://github.com/paritytech/polkadot-sdk/issues/8999
 - job-name: "zombienet-cumulus-0010-elastic_scaling_multiple_block_per_slot"
   test-filter: "zombie_ci::elastic_scaling::multiple_blocks_per_slot::elastic_scaling_multiple_blocks_per_slot"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 - job-name: "zombienet-cumulus-0011-dht-bootnodes"
   test-filter: "zombie_ci::bootnodes::dht_bootnodes_test"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "polkadot-parachain-debug"
   use-zombienet-sdk: true
 
@@ -76,13 +76,13 @@
 
 - job-name: "zombienet-cumulus-0013-elastic_scaling_slot_based_rp_offset"
   test-filter: "zombie_ci::elastic_scaling::slot_based_rp_offset::elastic_scaling_slot_based_relay_parent_offset_test"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
 
 - job-name: "zombienet-cumulus-0014-elastic_scaling_upgrade_to_3_cores"
   test-filter: "zombie_ci::elastic_scaling::upgrade_to_3_cores::elastic_scaling_upgrade_to_3_cores"
-  runner-type: "large"
+  runner-type: "default"
   cumulus-image: "test-parachain"
   use-zombienet-sdk: true
   needs-wasm-binary: true