Repository navigation
chore(release): bump version to 0.1.0-beta4 - #657
Merged
Merged
Conversation
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.
Summary
Related issue
Change type
Validation
pnpm test: 456 files, 2706 tests passedpnpm build: passedcargo fmt --manifest-path src-tauri/Cargo.toml --all -- --check: cleancargo clippy --manifest-path src-tauri/Cargo.toml --all-targets --all-features: passed, only the existing warnings in the sync testscargo test --manifest-path src-tauri/Cargo.toml --all-targets --all-features: 1853 tests, 0 failuresAlso:
pnpm verify:versionreports 0.1.0-beta4,node scripts/release-notes.mjs v0.1.0-beta4renders the notes, actionlint and zizmor report the same findings on release.yml as on main, and the metainfo is valid XML.OS/device: macOS (local checks only).
Screenshots or recordings
Risk and compatibility
No migrations, database, permission, playback or network changes.
Release workflow: tagged betas become the latest GitHub release, which is what installed apps update from. The beta build flavour (Flow Beta name and identifier) still follows the version.
No new secrets, private data, telemetry, or broad Tauri permissions were introduced.
User-facing documentation was updated where needed.
Dependency and lockfile changes are intentional and limited to this PR.
Breaking changes and upgrade steps are clearly documented.