Repository navigation
Rename package to @integration-testing/data-isolation for 0.1.0 - #5
Merged
Merged
Conversation
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.
Rename the unpublished package to @integration-testing/data-isolation@0.1.0. Update every package import, workspace dependency, Jest environment reference, runtime setup message, archive filename, verification script, and installation example. The repository name and public lifecycle/decorator APIs remain unchanged.
Add
test:consumer:publishedto install the exact release version from npm into a temporary application outside the workspace and run the real database matrix after publication. Default consumer checks continue using the packed artifact before release.Validation: full local verification, installed PostgreSQL/SQLite package checks, minimum Jest integration, and packed consumer matrix. Release CI must pass before merging and publishing. The old package name has not been published. npm authentication is being completed through the publishing account.