Skip to content

[ci] E: Update zutils#333

Merged
ppenna merged 3 commits into
mainfrom
automation/update-zutils-version
Jul 15, 2026
Merged

[ci] E: Update zutils#333
ppenna merged 3 commits into
mainfrom
automation/update-zutils-version

Conversation

@ppenna

@ppenna ppenna commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Automated update to nanvix/zutils v0.17.0. The target release implementation applied its own verified templates.

Copilot AI review requested due to automatic review settings July 15, 2026 15:05

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates this repository’s pinned nanvix/zutils version to align local/CI tooling with the referenced upstream release (v0.17.0), using the repo’s .zutils-version pin that z.sh/z.ps1 consume.

Changes:

  • Bump the pinned nanvix/zutils version from v0.16.3 to v0.17.0.
Show a summary per file
File Description
.zutils-version Updates the pinned nanvix/zutils release version used by the repo tooling wrappers.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Low

@ppenna ppenna force-pushed the automation/update-zutils-version branch from 6a9393d to 9eff28a Compare July 15, 2026 15:21
Copilot AI review requested due to automatic review settings July 15, 2026 20:05

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 8 out of 9 changed files in this pull request and generated 2 comments.

Comment thread .nanvix/src/setup.py Outdated
Comment on lines +35 to +38
# Magic-path naming (zutils v0.17.0):
# {pkg}-{host}-{arch}-{machine}-{mode}-{mem}.{ext}
dependency.artifact_pattern = (
"{name}-{host}-{arch}-{machine}-{mode}-{mem}.tar.gz"
Comment thread .nanvix/src/lib.py
Comment on lines +162 to +165
Matches ``nanvix-zutil release``'s magic-path naming
(``{pkg}-{host}-{target}-{machine}-{mode}-{mem}``) so that
``tar xf {archive}.tar.gz && cd {stem}`` lands the user inside
the extracted bundle.
github-actions Bot and others added 2 commits July 15, 2026 15:10
zutils v0.17.0 dropped release_targets() and release_dir() in favor of
staging directly under regular_out() / dev_out(). nanvix-python
publishes only a runtime archive, so everything is staged under
regular_out(). The resulting archive is auto-named:

  nanvix-python-linux-x86-microvm-standalone-256mb.tar.gz

and extracts as nanvix-python-linux-x86-microvm-standalone-256mb/, which
is the same string baked into the bundled README's 'cd {stem}' snippet.

Changes:

- src/lib.py: drop release_targets() override (obsolete). Update
  _asset_prefix() to include {host}-{target} so it matches the
  magic-path archive stem produced by nanvix-zutil release; this keeps
  the archive filename and the wrapping subdir inside the archive in
  sync so 'tar xf … && cd $stem' Just Works.
- src/build.py: bundle_dir = paths.regular_out() / asset_prefix.
- src/clean.py: paths.release_dir() -> paths.staging_dir() (covers
  both regular/ and dev/ subtrees).
- src/setup.py: update cpython dependency.artifact_pattern to the
  magic-path shape
  ('{name}-{host}-{arch}-{machine}-{mode}-{mem}.tar.gz') and pass
  {host}/{arch} to the matching prefix .format() call in
  _cached_cpython_artifact(). The old pattern
  '{name}-{machine}-{mode}-{mem}.tar.gz' no longer matched any asset
  in cpython's release.
- z.py: docstring updated (release_dir() -> regular_out()).
- Bump nanvix-version 0.20.0 -> 0.20.9, sdk-version v0.20.0-sdk.2 ->
  v0.20.9-sdk.1 (pulls cpython@3.12.3-nanvix-0.20.9-sdk.1 which ships
  linux + windows regular + -dev assets).
- Bump nanvix-ci.yml workflow ref v3.0.0 -> v3.0.1 (dual-host release).
@ada-x64 ada-x64 force-pushed the automation/update-zutils-version branch from 1286347 to 53657dc Compare July 15, 2026 20:10
zutils v0.17.0 magic-path names the CPython runtime archive
'.tar.gz' on linux hosts and '.zip' on windows hosts. buildroot's
Dependency.artifact_pattern only exposes {name}/{host}/{arch}/
{machine}/{mode}/{mem} (no {ext}), so we compute the extension from
config.host and inline it into the pattern.

Previously the pattern was pinned to '.tar.gz', which resolved fine
on linux but caused windows CI to fail with:

  Asset 'cpython-windows-x86-microvm-standalone-256mb.tar.gz' not
  found in release nanvix/cpython@…

The stale comment referencing a legacy 'Windows delivery bundle'
(with a pre-baked ramfs) is also dropped — that bundle no longer
exists under magic-path. The extension is still pinned rather than
prefix-matched to keep the sibling '-dev' archive out of the match.
Copilot AI review requested due to automatic review settings July 15, 2026 20:28

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 7 out of 8 changed files in this pull request and generated 2 comments.

Comment thread .nanvix/src/setup.py
# (which contains a ready-made ramfs rather than an extractable stdlib).
dependency.artifact_pattern = "{name}-{machine}-{mode}-{mem}.tar.gz"
# Magic-path naming (zutils v0.17.0):
# {pkg}-{host}-{arch}-{machine}-{mode}-{mem}.{ext}
Comment thread .nanvix/src/lib.py
Comment on lines +162 to +165
Matches ``nanvix-zutil release``'s magic-path naming
(``{pkg}-{host}-{target}-{machine}-{mode}-{mem}``) so that
``tar xf {archive}.tar.gz && cd {stem}`` lands the user inside
the extracted bundle.
@ppenna ppenna merged commit 11052b4 into main Jul 15, 2026
12 checks passed
@ppenna ppenna deleted the automation/update-zutils-version branch July 15, 2026 20:38
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.

3 participants