Repository navigation
test: verify packed consumer upgrades - #601
Merged
Merged
Conversation
|
ueberBrot
enabled auto-merge (squash)
October 8, 2026 11:15
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
Add an opt-in consumer check that installs packed packages outside workspace resolution and upgrades an existing Job collection.
The two
.mtsscripts run with Bun. The root TypeScript configuration checks their types against installed dependencies and built declarations; the copied consumer runs outside that configuration and resolves its own installed packages.This is a local command, not a CI gate. It requires Docker and registry access and writes its result to ignored
.verification/consumer.json. Usebun scripts/verification/consumer.mts --skip-buildto reuse package builds.Evidence
After: All three consumer combinations pass. Checks cover ESM/CommonJS entrypoints, authenticated Express and Dashboard HTTP assets, current TsED integration, preserved Job fields and index definitions, priority defaults, and repeated initialization.
Core 1.16.0 is the first published version satisfying the declared
^1.15.1peer range. Dashboard checks cover HTTP assets, not browser compatibility with older API combinations. These runs exercise Bun; they do not establish equivalent Node runtime compatibility.Merge Danger
Door: two-way
Revert the scripts, command, and TypeScript configuration changes to undo the change.
Blast Radius: tooling
The command uses temporary installs and disposable local MongoDB. Library runtime code is unchanged.