Skip to content

chore: release - #21

Open
h4x0r wants to merge 1 commit into
mainfrom
release-plz-2026-11-04T06-34-27Z
Open

h4x0r wants to merge 1 commit into
mainfrom
release-plz-2026-11-04T06-34-27Z

Conversation

@h4x0r

@h4x0r h4x0r commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

🤖 New release

  • memf-format: 0.3.2 -> 0.3.3 (✓ API compatible changes)
  • memf-strings: 0.2.3 -> 0.2.4 (✓ API compatible changes)
  • memf-correlate: 0.3.1 -> 0.3.2 (✓ API compatible changes)
  • memf-windows: 0.5.0 -> 0.5.1 (✓ API compatible changes)
  • memf-carve: 0.1.5 -> 0.1.6 (✓ API compatible changes)
  • memf-symbols: 0.2.4 -> 0.2.5
  • memf-core: 0.2.6 -> 0.2.7
  • memf-linux: 0.3.3 -> 0.3.4
  • memf-session: 0.3.3 -> 0.3.4
Changelog

memf-format

0.3.3 - 2026-11-04

Fixed

  • (security) state ruzstd >= 0.9.1 in memf-format's own manifest

memf-strings

0.2.4 - 2026-11-04

Fixed

  • (security) move to yara-x 1.22 and ruzstd 0.9.1

memf-correlate

0.3.2 - 2026-11-04

Fixed

  • (msrv) raise the memf-* floors to 1.89 (1.95 where yara-x reaches)

memf-windows

0.5.1 - 2026-11-04

Fixed

  • (security) move to yara-x 1.22 and ruzstd 0.9.1

memf-carve

0.1.6 - 2026-11-04

Fixed

  • (msrv) raise the memf-* floors to 1.89 (1.95 where yara-x reaches)

memf-symbols

0.2.4 - 2026-08-08

Fixed

  • clippy lints from the raised MSRV, and repair the rustdoc links

memf-core

0.2.5 - 2026-08-08

Fixed

  • clippy lints from the raised MSRV, and repair the rustdoc links

memf-linux

0.3.3 - 2026-08-08

Fixed

  • clippy lints from the raised MSRV, and repair the rustdoc links


This PR was generated with release-plz.

@h4x0r
h4x0r force-pushed the release-plz-2026-11-04T06-34-27Z branch from a36b9a7 to 365ef2d Compare November 4, 2026 17:02
h4x0r pushed a commit that referenced this pull request Nov 4, 2026
bdf1c99 raised the workspace ruzstd to 0.9.1 (RUSTSEC-2026-0344), but
memf-format inherited it (`ruzstd.workspace = true`), so no file in the
crate changed and release-plz did not release it: PR #21 bumps carve,
correlate, strings and windows only. crates.io's memf-format 0.3.2 still
requires ruzstd ^0.8, so every consumer (4n6mount, browser-forensic,
issen) would keep the decompression bomb even after the release.

memf-format, the only ruzstd user, now declares `ruzstd = "0.9.1"`
itself, with the reason, and the unused workspace entry is removed. The
packaged manifest (`cargo package -p memf-format`) carries
dependencies.ruzstd version "0.9.1". Lockfile unchanged. 147 memf-format
tests pass; builds on its 1.89 floor; fmt, clippy, cargo deny and cargo
vet pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@h4x0r
h4x0r force-pushed the release-plz-2026-11-04T06-34-27Z branch from 365ef2d to 6ee594f Compare November 4, 2026 17:54

This branch has not been deployed

No deployments
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.

1 participant