fix(release): use npm semver for cohort checks - #1160
Closed
drewstone wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Closing: this release-check cleanup introduced a semver dev-dependency unavailable in the packed-cohort job. The underlying prerelease arithmetic issue is real, but it needs a separately designed dependency/workflow change; do not merge this scope into the current research delivery. |
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
semverlibrary for package cohort admission checksEvidence
pnpm run lint: passpnpm run typecheck: passpnpm run build: passpnpm run verify:package: passgit diff --check: passThis is dev-only release verification; Runtime execution behavior is unchanged.