Repository navigation
Bump version to 0.8.0 - #100
Merged
Merged
Conversation
Opens the 0.8 changelog section with everything merged since v0.7, and moves the #95/#97 and #98 entries into it -- both were written into the already-released 0.7 section by mistake. New in 0.8: the --sanitize recycled-block false positives (#95/#97), the --ram-versus-CPU-address-bus check (#98/#99), pr_Arguments on the fake Process (#89), AllocDosObject's DOS_FIB (#90), SetVar on a missing variable (#91), and OpenLibrary's CMP.W version comparison (#92). The three m68k crate bumps (#88/#93/#94) get no entry, as dependency updates never have. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Release prep for 0.8, same shape as #87 was for 0.7: version bump in both crates (plus
Cargo.lock) and a## 0.8changelog section.Note on the changelog
Two entries needed moving, not just adding. The #95/#97 and #98 work went into the
## 0.7section, which was already tagged and released on 2026-09-16 — they are now under## 0.8where they belong.## 0.7is back to exactly what shipped in it.What is in 0.8
--sanitizeno longer reports a recycled heap block as use-after-free (--sanitize: recycled heap block keeps its freed-block poison, so a fresh AllocVec reports use-after-free and runs ~75x slower #95, reported by @codewiz → sanitize: clear recycled-block poison in the heap, not per handler #97)--ramabove what the configured CPU can address is refused up front (--ram above 16 MiB silently breaks 68000/68010 runs: guest stack is placed beyond the 24-bit address bus #98 → Refuse --ram above what the configured CPU can address (issue #98) #99)pr_Argumentspopulated on the fakestruct Process(Populate pr_Arguments on the fake struct Process #89)AllocDosObject/FreeDosObjectsupportDOS_FIB(Implement AllocDosObject/FreeDosObject's DOS_FIB type #90)SetVar/DeleteVaron a missing variable succeed silently (Fix SetVar to succeed silently on a missing variable #91)OpenLibraryignores garbage in the requested version's high word, matching real ROMs'CMP.W(Match real Kickstart's CMP.W version check in OpenLibrary #92)The three m68k crate bumps (#88, #93, #94) get no entry, matching how dependency updates have always been treated.
Checks
cargo test --release1014 passed, 0 failed; clippy-D warningsandfmt --checkclean;volamos fixtures/helloruns.After merge
git tag v0.8 && git push origin v0.8— that is the whole trigger. The tag fans out to the release jobs inci.yml(Linux musl x86_64/aarch64, macOS aarch64, Windows gnu, multi-arch Docker image) andrelease-publishcreates the GitHub release with--generate-notes;docs.ymldeploys the docs as versionv0.8plus the floatinglatestalias.🤖 Generated with Claude Code