Repository navigation
Prepare @integration-testing/data 0.1.0 for npm publication - #4
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.
Prepare the first
@integration-testing/datarelease as 0.1.0 on npm'slatesttag. Update package metadata and descriptive search keywords, changelog, README installation examples, and first-publication instructions. The release workflow defaults tolatestand only runs its publishing job onmain.Scope is the documented Jest/Vitest transactional testing API with PostgreSQL through pg, Prisma, or TypeORM and SQLite through Prisma. Shared Testcontainers Integration 0.1.0 provisioning remains optional. Generated file-owned container setup, automatic HTTP interception, and concurrent tests within a file remain unsupported.
Validation: dependency audit, 25 unit tests, 42 current-runner subprocess cases, 42 minimum-Jest cases, ESM/CommonJS runtime and types, optional dependency independence, installed Docker/SQLite examples, and the independent consumer matrix including 38 deliberately failing database processes, external URLs, and parallel file ownership. The exact final archive passes npm publish dry-run, includes 82 files, and excludes repository examples. Final commit CI passed.
Prepared archive:
.artifacts/integration-testing-data-0.1.0.tgz; SHA-256c43f7fd92151f7b9dacc6e57411bea61f746706ff9ce4940585b4a03fbfd8de9.npm reports 0.1.0 available for publication. No publication was performed. The local npm session is unauthenticated, so the first upload requires an authorized npm account. The GitHub
npmenvironment exists; package-specific trusted publishing must be configured after bootstrap publication. Merge and verify the final main commit before publishing.