chore: release devtools 0.3.5 - #417
Merged
Merged
Conversation
✅ Deploy Preview for cn-devtools-app canceled.
|
beanow-at-crabnebula
marked this pull request as draft
September 11, 2026 14:01
beanow-at-crabnebula
force-pushed
the
beanow/fix-v1-release-plz
branch
2 times, most recently
from
September 11, 2026 14:05
7ea2bf7 to
b656ca1
Compare
beanow-at-crabnebula
force-pushed
the
beanow/fix-v1-release-plz
branch
from
September 11, 2026 15:49
2a96417 to
77f128c
Compare
beanow-at-crabnebula
marked this pull request as ready for review
September 11, 2026 15:49
david-crabnebula
approved these changes
Sep 11, 2026
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.
🧑🦲 New release
devtools: 0.3.4 -> 0.3.5 (✓ API compatible changes*)Notes
Manually generated and reviewed release, because
devtools-core 0.3.7currently exists and causes a CI to fail on release PR generation.*=Regarding API compatibility, I found technically we re-export the
devtools_core::Errortype, which exposes a Tonic error variant. If you're using your own import oftonic 0.10.xand were comparing / matching against this it may now be different types.This was true as well of the
tauri-plugin-devtools 2.2.0and2.2.1releases. This isn't considered breaking by thecargo-semver-checksthat CI normally does.