Skip to content

[ci] E: Update Nanvix SDK - #333

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

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

Conversation

@ppenna

@ppenna ppenna commented Jul 30, 2026

Copy link
Copy Markdown

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

Copilot AI review requested due to automatic review settings July 30, 2026 11:50

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.

Pull request overview

Updates the Nanvix SDK configuration used to build this repository on Nanvix by bumping the pinned Nanvix version and corresponding SDK image digest/lock metadata to a newer verified release.

Changes:

  • Bump nanvix-version from 0.21.51 to 0.21.53.
  • Bump sdk-version from v0.21.51-sdk.1 to v0.21.53-sdk.1 and update the pinned SDK image digest.
  • Regenerate .nanvix/nanvix.lock to reflect the new resolved Nanvix/zlib artifacts and toolchain metadata.
Show a summary per file
File Description
.nanvix/nanvix.toml Updates the pinned Nanvix + SDK version and SDK image digest used by builds.
.nanvix/nanvix.lock Updates the resolved lock metadata (hashes, digests, commits, asset URLs/IDs) to match the new SDK version.

Review details

Tip

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

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

@ppenna
ppenna merged commit 6d65a60 into nanvix/v3.49.0 Jul 30, 2026
13 checks passed
@ppenna
ppenna deleted the automation/update-nanvix-version branch July 30, 2026 11:53
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