Repository navigation
release: prepare the Node disagreement loop as 3.5.0 - #192
Merged
Merged
Conversation
Client and backend 3.5.0 and CLI 0.8.0 sit in the in-flight window so the check, the finding, and the API Client handoff can be installed. Examples stay on the published artifacts until those three exist. Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
The workspace packages are 3.5.0, so the examples that stay on the published artifacts need their own registry entries or npm ci rejects the lockfile. Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
3.5.0 changes the default validation result inside the 3.x range, and it is the first client, backend, and CLI release whose package metadata is Apache-2.0. The notes say both, and they do not rewrite tarballs already on the registry. Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
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
@prauga/flexdoc-clientand@prauga/flexdoc-backendat 3.5.0 and@prauga/flexdoc-cliat 0.8.0 in the version contract's in-flight window.flexdoc validateby name, acknowledgement stays informational without dropping the route, and the finding opens in the API Client fromserverOriginonly.Test plan
node scripts/check-example-versions.mjsreports client, backend, and CLI in flight and examples still on published baselinesnode scripts/check-release-doc-version-claims.mjsmatches source 3.5.0 / CLI 0.8.0 against published client 3.4.0js/v3.5.0andcli/v0.8.0only. The repin is a follow-up once those artifacts exist