Skip to content

[ci] E: Update Nanvix SDK - #363

Merged
ppenna merged 1 commit into
nanvix/v3.49.0from
automation/update-nanvix-version
Sep 4, 2026
Merged

[ci] E: Update Nanvix SDK#363
ppenna merged 1 commit into
nanvix/v3.49.0from
automation/update-nanvix-version

Conversation

@ppenna

@ppenna ppenna commented Sep 4, 2026

Copy link
Copy Markdown

Automated coherent update to verified Nanvix SDK v0.24.14-sdk.1. The manifest and lockfile were generated atomically by the target zutils implementation.

Copilot AI lite review requested due to automatic review settings September 4, 2026 13:58

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The manifest and lockfile changes are consistent, syntactically valid, and appear to be an atomic version/digest bump with no code-path impact beyond toolchain pinning.

Review tier: Lite
Findings: None

What changed in this PR

Updates the repository’s Nanvix build/toolchain configuration to use the verified Nanvix SDK v0.24.14-sdk.1, keeping the manifest and lockfile aligned for reproducible CI/toolchain resolution.

Changes:

  • Bumped nanvix-version from 0.24.12 to 0.24.14 in the Nanvix manifest.
  • Updated SDK pin (sdk-version) and container image digest to v0.24.14-sdk.1.
  • Regenerated nanvix.lock to reflect the new SDK/sysroot/toolchain commit and updated dependency asset references (zlib).
File Description
.nanvix/​nanvix.toml Updates the Nanvix SDK/version and image digest pins in the manifest.
.nanvix/​nanvix.lock Regenerates the lockfile metadata and resolved artifacts to match SDK v0.24.14-sdk.1.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ppenna
ppenna merged commit fa176b1 into nanvix/v3.49.0 Sep 4, 2026
13 of 14 checks passed
@ppenna
ppenna deleted the automation/update-nanvix-version branch September 4, 2026 14:01
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