Skip to content

chore(main): release bindings 0.16.0 - #819

Merged
TomWambsgans merged 1 commit into
mainfrom
release-please--branches--main--components--bindings
Nov 20, 2026
Merged

TomWambsgans merged 1 commit into
mainfrom
release-please--branches--main--components--bindings

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.16.0 (2026-11-20)

Features

  • VRF tree, with pruning + with a cached middle layer (#805) (c38f2ba)

Bug Fixes

  • staged native archives carry no LLVM bitcode, which Go 1.27 refuses (41ca15b)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot changed the title chore(main): release bindings 0.15.1 chore(main): release bindings 0.16.0 Nov 20, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--bindings branch from 9a34926 to e4aa570 Compare November 20, 2026 21:37
@TomWambsgans
TomWambsgans merged commit 241b009 into main Nov 20, 2026
@TomWambsgans
TomWambsgans deleted the release-please--branches--main--components--bindings branch November 20, 2026 21:38
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

TomWambsgans added a commit that referenced this pull request Nov 20, 2026
The release PR (#819) was merged before sync-cargo-lock could push the lock bump to its branch, so main's lock kept the workspace crates at 0.15.0 and Bindings CI's lock check fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TomWambsgans added a commit that referenced this pull request Nov 20, 2026
…go.lock

The lock was bumped only by sync-cargo-lock, pushing to the release PR's branch after release-please updated it; merging the PR first (#819) left main's lock at the previous version and Bindings CI's lock check red. release-please now edits the four workspace crates' lock entries in its own commit, as it does bindings/Cargo.toml. Its TOML parser wraps each value, so the filters compare @.name.value as well as @.name.

Tested with release-please 17.3.0 (what release-please-action v4 bundles) and 17.11.2: from the 0.15.0 lock, the config's four entries change exactly the four version lines, giving the lock of 001c9dc byte for byte. sync-cargo-lock stays as a fallback until a release PR shows it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant