docs(paseo-omp): document stable release channel - #271
Merged
Merged
Conversation
Replace alpha preview wording with stable in README, SUPPORT, installation and testing docs. Rename the alpha release checklist to release-checklist. Drop the inert prerelease and prerelease-type keys from the paseo-omp release-please entry: without a prerelease versioning strategy they have no effect on 1.x releases.
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
README.md,SUPPORT.md,docs/installation.md,docs/core-provider-issue-audit.mdandTESTING.md.docs/alpha-release-checklist.mdtodocs/release-checklist.mdand make its version, tag and limitation text release-generic.prereleaseandprerelease-typefrom thepaseo-ompentry inrelease-please-config.json.Why the config change is safe
Release Please only applies these keys through the
prereleaseversioning strategy, which needs"versioning": "prerelease"; this config sets none. The 1.x releases are normal GitHub releases and npmlatestis 1.2.0, so the keys were inert and only misleading.v0.4.0was the last release flagged Pre-release, matching the pre-major rule.Verification
paseo-ompfull vitest suite: 848 passed, 7 skipped.tests/server-bundle.test.ts, the only test reading the release config and README, passes.