Skip to content

Update skale.py-core to 8.0dev3 and helper-scripts to f3324bd - #1003

Merged
dmytrotkk merged 1 commit into
developfrom
update-skale-py
Nov 18, 2026
Merged

dmytrotkk merged 1 commit into
developfrom
update-skale-py

Conversation

@dmytrotkk

Copy link
Copy Markdown
Member

Moves node-cli to skale.py-core 8.0dev3 and the helper-scripts submodule to helper-scripts develop. No code changes.

  • skale.py-core 8.0dev0 → 8.0dev3 (pyproject.toml): the skale_core package is identical in the two wheels and keeps the same requirements (pydantic-settings>=2.14.2, tomli-w>=1.2.0), so skale_core.settings and skale_core.types, which node-cli imports, are unchanged. The resolved runtime set differs from develop only in skale-py-core.
  • helper-scripts gitlink c1f67269 → f3324bde (helper-scripts develop, including Support modern SKALE Manager deployments helper-scripts#49 and Update foundry, redis and Python requirements helper-scripts#50): run_anvil moves from foundry v1.4.0 → v1.9.0, redis/run.sh from redis 8.0.1 → 8.10.3, deploy_manager runs yarn hardhat and stops early when the Manager image writes no contracts file, load_geth.py and the GANACHE_VERSION export are gone, and requirements.txt moves boto3 1.13.7 → 1.44.1, drops pyyaml 5.4 and adds jinja2 3.1.6. This repo only uses calculate_version.sh (publish.yml), which is byte-identical between the two commits, and helper-scripts is not part of the builder image (.dockerignore).

node-cli pins no MANAGER_TAG and no sgxwallet simulator image, so those parts of the round do not apply here. Independent of #1000, which edits other lines of pyproject.toml; the two merge without conflict.

Tested locally
The test.yml and audit.yml jobs ran step by step in an amd64 Ubuntu 24.04 Docker-in-Docker runner on Apple Silicon, not on GitHub, with uv 0.13.8 instead of the pinned 0.13.6. On CPython 3.14.10, uv sync --all-extras installs skale.py-core 8.0dev3, and ruff check passes. The node-cli-builder image builds, PyInstaller 6.22.3 builds the skale and fair binaries, and both print their help with exit 0. The nftables tests give 45 passed. The first run of the tests gave 289 passed and 2 failed, both because of the runner image: it had no tzdata, so tests/cli/schains_test.py::test_ls, which sets TZ=Europe/London, printed times in UTC, and no btrfs binary, which tests/core/core_schains_test.py::test_cleanup_passive_datadir runs through is_btrfs_subvolume. With tzdata and btrfs-progs installed in the runner, the tests give 291 passed, the same counts as the last develop run on GitHub (44156254848, at ba4051e). pip-audit 2.10.1 (OSV) on the audit.yml export finds no known vulnerabilities.

Not run: the GitHub jobs themselves and publish.yml, which runs on merge and is the only workflow that uses the helper-scripts submodule.

Part of skalenetwork/skale-node#891

@dmytrotkk
dmytrotkk merged commit 33a6e27 into develop Nov 18, 2026
3 checks passed
@dmytrotkk
dmytrotkk deleted the update-skale-py branch November 18, 2026 19:16
@dmytrotkk dmytrotkk mentioned this pull request Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants