Bump version to 0.7.0 - #87
Merged
Merged
Conversation
v0.7's theme is that volamos can now find bugs in the programs it runs, not just run them. The `## Unreleased` section becomes `## 0.7`: - `--sanitize-uninit` (#68), opt-in uninitialized-read detection, plus `--sanitize-ignore-pc` and per-PC report grouping. - `--dirty-heap` (#80), filling non-MEMF_CLEAR allocations so a program relying on uncleared memory being zero fails here as it can on real hardware. - Source locations in diagnostics (#74): `file:line` from HUNK_DEBUG LINE blocks, `symbol+offset` from HUNK_SYMBOL otherwise. - Four more allocators covered by the heap detectors (#83 tier 0). Note the changelog has a second, historical "## Unreleased (0.1, in development)" heading further down, so the rename has to target the exact `## Unreleased` line rather than the substring. Tagging v0.7 is what publishes: release binaries for four targets, the Docker image, and the versioned docs site. That last one matters more than usual this time -- userdocs/Differences-from-vamos.md has been on main since #78 but 404s on the published site, because docs only deploy on a tag. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AKBJRT9j5APTyKyZtj8f23
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 v0.7, whose theme is that volamos can now find bugs in the programs it runs, not just run them.
Bumps both crates and
Cargo.lockto0.7.0, and renames## Unreleasedto## 0.7:--sanitize-uninit, plus--sanitize-ignore-pcand per-PC report grouping--dirty-heapfile:line/symbol+offsetin diagnosticsOne footgun worth noting for next time: the changelog has a second, historical
## Unreleased (0.1, in development)heading further down, so the rename has to target the exact## Unreleasedline rather than the substring — my first attempt tripped its own assertion on that.Verification
cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo test --all(1002 tests) andmkdocs build --strictall pass — exit codes checked directly, not through a pipe. Release-profile binary smoke-tested: runsfixtures/helloand still catches thememtest overrun.After merge
Tagging
v0.7is what publishes: release binaries for four targets, the Docker image, and the versioned docs site. That last one matters more than usual here —userdocs/Differences-from-vamos.mdhas been onmainsince #78 but still 404s on the published site, because docs only deploy on a tag.🤖 Generated with Claude Code
https://claude.ai/code/session_01AKBJRT9j5APTyKyZtj8f23