chore(release): run the full unit suite in the npm release gate - #60
Merged
Conversation
The release workflow used to skip the unit suite because a few specs were flaky; those were de-flaked (#59), so the publish gate now runs `nx test nestjs` — the tag you publish must pass its own tests. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
Now that the flaky specs are de-flaked (#59), the npm release workflow no longer needs to skip the unit suite. Adds a
nx test nestjsstep (and updates the stale comment) so the tag you publish must pass its own tests — one of the 1.0-bar items.🤖 Generated with Claude Code