Repository navigation
release: 0.5.0-beta.1 - #1712
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.
First Beta release: 0.5.0-beta.1, prepared with
scripts/release/prepare_beta.sh 0.5.0 1(#1499).pubspec.yaml:0.4.22+5→0.5.0-beta.1+6.CHANGELOG.md:## [Unreleased]became## [0.5.0-beta.1] - 2026-10-18, and the 33 merges since the last changelog commit (the Beta channel itself, the pre-update backup and newer-schema guard, the macOS work, query errors, the SQL splitter security fix, the performance and bug fixes) are written into its Added / Changed / Fixed sections.scripts/release/check_release.sh 0.5.0-beta.1passes: SemVer tag, pubspec matches, changelog section present, tag free. TheRelease branch checkjob runs the same on this PR.After this is merged the tag
0.5.0-beta.1goes on the merge commit and the Release workflow publishes a GitHub pre-release (not Latest, no AUR, no APT / DNF). Check afterwards:gh release view 0.5.0-beta.1 --json isPrerelease, and thatreleases/lateststill returns 0.4.19.This is the first run of the beta pipeline, so it doubles as the dry run: whether macOS / Windows builds accept
-beta.1in their version fields is not known until it runs. If a job fails, the pre-release can be deleted and the tag re-cut as0.5.0-beta.2(a failed tag is not reused).The version stays
0.5.0-beta.1+6ondevafter the merge;version-bump.ymlleaves a pre-release version alone, and the promote step (version: 0.5.0+B) is in docs/tags-and-releases.md.