fix(tailordb): make migration hint commands shell-safe - #1985
Merged
toiroakr merged 1 commit intoAug 6, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: ab23d97 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@tailor-platform/create-sdk
@tailor-platform/eslint-plugin-sdk
@tailor-platform/sdk
@tailor-platform/sdk-plugin-seed
@tailor-platform/sdk-plugin-tailordb-erd
commit: |
toiroakr
merged commit Aug 6, 2026
e43d35e
into
feat/tailordb-migration-validate-strict
38 checks passed
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
Copyable migration-script hint commands — from
migration generate,migration validate --strict, and deploy's missing-script error — are rendered by one shell-aware formatter, so a config path that Windows shells would expand no longer produces a hint that silently targets a different file.Before / After
With a config path containing
%on Windows:--config "C:\work\%APP%\tailor.config.ts"— cmd.exe/PowerShell expand%APP%even inside double quotesargv ["tailor","tailordb","migration","script","0001","--namespace","tailordb","--config=C:\\work\\%APP%\\tailor.config.ts","--no-script","--reason","<reason>"]This matches how
Next:commands in CLI errors already degrade on Windows.Deploy hint changes
The deploy missing-script error now shares the same formatter, which also changes its hint:
script 0001, previouslyscript 1)--configis bound with the=form and omitted when it resolves to the defaulttailor.config.ts<reason>Notes