release: 1.0.0-rc.5 - #282
Merged
Merged
Conversation
nicksinas
approved these changes
Sep 18, 2026
There was a problem hiding this comment.
🟢 Approval recommended
The changes are limited to a consistent version bump and changelog promotion with no functional code modifications.
Pull request overview
Cuts the 1.0.0-rc.5 release by promoting the changelog’s [Unreleased] notes into a dated release section and aligning the crate version across the Rust manifest and lockfile.
Changes:
- Promoted
[Unreleased]entries to## [1.0.0-rc.5] - 2026-09-17inCHANGELOG.md(leaving an empty[Unreleased]section for the next cycle). - Bumped
avocado-cliversion from1.0.0-rc.4to1.0.0-rc.5inCargo.toml. - Updated the
avocado-clipackage entry inCargo.lockto1.0.0-rc.5.
File summaries
| File | Description |
|---|---|
| CHANGELOG.md | Moves release notes from [Unreleased] into the 1.0.0-rc.5 section with the release date and consolidated headings. |
| Cargo.toml | Bumps the crate version to 1.0.0-rc.5. |
| Cargo.lock | Updates the locked avocado-cli package version to 1.0.0-rc.5. |
Review details
- Files reviewed: 2/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Cut
1.0.0-rc.5: the[Unreleased]changelog section becomes## [1.0.0-rc.5] - 2026-09-17, and the crate version moves from1.0.0-rc.4to1.0.0-rc.5inCargo.tomlandCargo.lock.Release notes
The rc.5 section of
CHANGELOG.mdis the release notes. It covers the nine PRs merged since rc.4, grouped Changed / Fixed / Security. This is a bug-fix release for regressions found in the rc.4 phase:avocado installruns the SDK phase in parallel without--force, with one parallelism rule shared by the install DAG, the build DAG and the SDK phase (install: one parallelism rule for the DAGs and the SDK phase #275).Failed to walkcrash inext build(Fix project-relative path resolution for a bare config filename #274), the compile-script failure for package-sourced extensions (Skip the compile script for a source the host cannot see #271), the--dnf-arginstall stamp deletion that made a project unbuildable (ext install: keep the install stamp after a --dnf-arg transaction #272), a stamp path that was not one shell word (ext install: keep the install stamp after a --dnf-arg transaction #272),ext buildskipping an extension whose content comes from apost_buildhook (ext build: rebuild an extension whose post_build inputs are undeclared #279), the i.MX bootloader deleted by the re-key cleanup glob plus multi-pathstone_include_paths(runtime build: re-key into a directory the build owns, not the dnf install root #281), and the build-time kernel cmdline export deleted by a merge, now covered by the runtime build stamp (fix(kernel): restore the build-time kernel cmdline export #277).cryptoki0.12.1 for RUSTSEC-2026-0286 (build(deps): cryptoki 0.12.1 for RUSTSEC-2026-0286 #278), and the extension source symlink guard re-armed on the default config path (Fix project-relative path resolution for a bare config filename #274).Every bullet that was under
[Unreleased]onmainis present; the two### Fixedheadings that had accumulated there are merged into one, and entries were added for the PRs that landed without a changelog line (#271, #274, #275, #277, #278). An empty[Unreleased]heading remains for the next cycle.After merge
Tag the squash commit
1.0.0-rc.5to run the release workflow. TheBump Homebrew tap formulajob will fail as it did for rc.4:homebrew-tapmainnow requires a pull request, so the formula bump has to be opened by hand from theSHA256SUMSasset (rc.4's is still open as homebrew-tap#1).Verification
fmt, clippy (
-D warnings) and the version guard test pass on this branch; the version guard reads1.0.0-rc.5.cargo metadata --lockedagrees with the lockfile.Smoke test of this exact commit against the
jetson-orin-nano-devkitreference project, 2024/edge feed:avocado clean -f,avocado install -f,avocado buildfrom a fresh volume, all exit 0; rootfs, initramfs, stone validate/create and the OS bundle produced.avocado install -f,avocado build,avocado provision -r dev --profile tegraflash, all exit 0; the flash ran hands-off in under four minutes and the board booted with the built image'sAVOCADO_OS_BUILD_ID, all four extensions merged, sshd up.