chore(release): 1.0.0-alpha3 - #349
Merged
Merged
Conversation
…g else derives Same eight files as the alpha2 bump, by the same mechanism - the root package.json is the single source publish-gates.mjs reads, and every workspace and the lockfile follow it. The four-way match that gates a publish is filename == package == verdict == tag, so this has to land before v1.0.0-alpha3 is cut, not alongside it. Since alpha2, master has gained the two lost-work defects fixed in #348: a watcher broadcast that could be older than the write it landed after, which the preferences tabs then wrote back to disk, and a preferences window that accepted edits before it had loaded, which made "revert to how this window opened" restore the value being discarded.
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
1 participant
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.
Version bump only — the same eight files as the alpha2 bump, by the same mechanism. The root
package.jsonis the single sourcepublish-gates.mjsreads; every workspace and the lockfile follow it.This has to land before
v1.0.0-alpha3is cut rather than alongside it, because the publish gate is a four-way match: installer filename == package version == verification verdict == release tag.What alpha3 carries over alpha2
The two lost-work defects fixed in #348, both found while chasing the
@prefs @reserve:windowflake family:Both shipped with regression tests at the cheapest layer that shows them, each watched failing against the unfixed code first.
Release state
masteratdb252dbbhas both CI and Release green — so the full E2E suite, the installer build and the clean-runner install verification have already passed on the commit this bump sits on top of.Once this merges, the tag
v1.0.0-alpha3gets cut on master. The publish job then stops for thereleaseEnvironment's required reviewers, which is the human QA sign-off (FR-029) and is not bypassable from a developer machine (FR-037).