chore(main): release 0.18.0 - #1830
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
29 times, most recently
from
August 18, 2026 11:14
6226e34 to
7127923
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
18 times, most recently
from
August 24, 2026 20:09
e1b8e0b to
5c41615
Compare
This was referenced Aug 24, 2026
tato123
added a commit
that referenced
this pull request
Aug 24, 2026
…them (#1955) * fix(ci): sync the in-tree version pins at the release bump, and gate them The Release workflow has failed on every one of the last 20 pushes to main, and it is the only failure there. `release-please`'s `simple` release type bumps `[workspace.package] version` and ships no cargo dependency-requirement updater, so the 45 in-tree `{ path = "…", version = "…" }` pins sit still while the crates they name move. Within a minor line that is invisible — `^0.17.0` matches `0.17.1` — but `^0.17.0` excludes `0.18.0`, so the release branch holds a workspace that cannot resolve at all and `cargo update --workspace` exits 101. The auto-merge step never runs, no tag is cut, and `trigger-wheel-release` is skipped. Release PR #1830 has been open since 2026-08-11 for exactly this reason, and the PEP 503 index still tops out at 0.17.1. The sync step's own comment always claimed it rewrote the requirements; only `cargo update` was ever there. Move the pins first, with a gate holding the same rule on every PR so the drift can only ever appear at the bump. `cargo` resolves the whole workspace before building any member, so the sync tool cannot be built once the bump has landed — the resolve it repairs is the one that fails. It is built while main still resolves and the binary is run against the release branch. `[workspace.package].version` and `.release-please-manifest.json` are untouched and stay release-please's alone; only the dependency requirements move. Closes #1954 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix(ci): make the version-pin scan TOML-section aware The first cut matched dependency lines by shape alone, so `[dependencies.streamlib-error]` — path and version on their own lines — was invisible to it. A pin the gate cannot see is a pin that reaches the release branch, which is the exact failure this gate exists to prevent, and it would have failed silently. Walk the table headers instead: a dependency entry is now one stated inside a dependency table, in either spelling, including the target-specific and workspace forms. `[lib]` and `[[test]]` paths fall out for free, since they live outside every dependency table rather than being excluded by shape. Scope the inherited-version check to `[package]` for the same reason — a `version.workspace = true` under a `[package.metadata.…]` table an external tool owns must not answer for the crate. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
August 24, 2026 22:46
5c41615 to
3967e20
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
0.18.0 (2026-08-24)
⚠ BREAKING CHANGES
Texture::native_handle()returns a DMA-BUF fd whose ownership transfers to the caller; previously the texture closed it at drop. No in-tree caller exists.streamlib::schemas::current_schema_identsandcurrent_schema_definitionare removed, along with theGET /api/schemasandGET /api/schemas/{name}control-plane endpoints.Features
Bug Fixes
Performance
Code Refactoring
Documentation
Miscellaneous
This PR was generated with Release Please. See documentation.