Repository navigation
Conversation
Node refuses to strip TypeScript from files under node_modules, so the published omniroute CLI could fail before startup on global installs. Replace the packaged bin entry with omniroute.mjs, add a runtime-support bridge, and update pack-artifact coverage so the published tarball keeps the executable files reviewers should expect.
The mass-migration safety abort was firing on real 001-era databases because startup pre-seeding made them look like an existing DB with too many pending migrations. Infer the baseline from physical schema sentinels before aborting, keep blocking suspicious tracking-loss cases, and cover both paths with focused migration-runner tests.
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
diegosouzapw
added a commit
that referenced
this pull request
Apr 17, 2026
Collaborator
|
Thanks for this contribution! 🎉 The CLI runner split and migration engine decoupling have been integrated into the |
Merged
This was referenced Apr 30, 2026
Merged
Merged
Merged
Poid-ZA
pushed a commit
to Poid-ZA/OmniRoute
that referenced
this pull request
Aug 5, 2026
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
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.
I found a bug when I installed on windows by npm.
version 3.6.7
But there is a problem about DB, so I fixed that problem.
This pull request introduces a significant improvement to the database migration safety checks by inferring the physical schema version directly from the database, allowing for more robust handling of pending migrations and preventing accidental data loss. Additionally, it updates references and packaging policies to reflect the renaming of the main CLI entry point from
bin/omniroute.tstobin/omniroute.mjsacross the codebase and tests.Database migration safety and testing improvements:
migrationRunner.tsto infer the physical schema version from existing tables, allowing the migration runner to distinguish between legitimate upgrades and potential data loss scenarios. This includes new sentinel definitions, detection functions, and revised safety checks to allow or abort large pending migration sets based on the detected schema baseline. [1] [2] [3]db-migration-runner.test.tsto verify the new schema inference logic, including scenarios where migrations are allowed or aborted based on the physical schema, and added utility functions for test setup. [1] [2]CLI entry point and packaging updates:
bin/omniroute.tstobin/omniroute.mjsinpackage.json, artifact policy scripts, and tests to ensure consistency and correct packaging. [1] [2] [3] [4] [5] [6] [7]Minor code quality improvements:
These changes collectively enhance the reliability of database migrations, ensure proper CLI packaging, and improve test coverage and clarity.