Repository navigation
chore: move the release version line to 0.6 - #60
Merged
Merged
Conversation
Bump RELEASE_VERSION_LINE so stable releases publish from the 0.6.x line, parameterize the channel error messages around the line constant, and move the release test fixtures and workflow examples to 0.6.x versions.
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.
Summary
RELEASE_VERSION_LINEto0.6inscripts/release/policy.mjsso stable releases can publish from the 0.6.x line.release-policy,publisher,release-package) and the workflow input example to 0.6.x versions.Why
The next release carries the accumulated 0.5.0..main delta — three SDK cohort upgrades (1.0.0-rc.0, 1.0.2, 1.0.3), the
.univerv3 data format, the newprint-pdfcommand, and unit-comparison-viewer localization — which warrants a minor rather than a patch.channelForVersion("0.6.0")previously rejected with "must stay on the 0.5.x version line".Test plan
vitest run test/release-policy.test.ts test/publisher.test.ts test/release-package.test.ts test/release-workflow.test.ts— 12 passedpnpm check— format/lint/typecheck/check:locales/test/pack:check all green on this branch (one pre-existing flaky locale test times out under host load spikes on unmodified main too; it passes in ~1.1s idle here, see chore: upgrade Univer SDK to 1.0.3 #59 notes for the baseline evidence)