Skip to content

chore: link the tsup baseUrl workaround to its upstream issue/PR - #27

Merged
zanlucathiago merged 1 commit into
mainfrom
chore/link-tsup-workaround
Jul 6, 2026
Merged

chore: link the tsup baseUrl workaround to its upstream issue/PR#27
zanlucathiago merged 1 commit into
mainfrom
chore/link-tsup-workaround

Conversation

@zanlucathiago

Copy link
Copy Markdown
Owner

Our ignoreDeprecations: "6.0" in tsconfig.json is a workaround for tsup unconditionally injecting baseUrl: "." into its DTS build (deprecated in TS 6, removed in TS 7).

This just annotates the line with the upstream tracking so a future reader knows exactly when it can be removed:

Verified locally that PR #1390's one-line fix makes our DTS build pass on TypeScript 6.0.3 without ignoreDeprecations, and left a tested confirmation on that PR. No code change here — comment only.

🤖 Generated with Claude Code

The `ignoreDeprecations: "6.0"` line exists only because tsup's DTS build injects
a default `baseUrl` (deprecated in TS 6, removed in TS 7). Reference the upstream
tracking so we know when the workaround can go: egoist/tsup#1388, fixed by
egoist/tsup#1390.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@zanlucathiago
zanlucathiago merged commit a4ad931 into main Jul 6, 2026
3 checks passed
@zanlucathiago
zanlucathiago deleted the chore/link-tsup-workaround branch July 6, 2026 18:34
zanlucathiago added a commit that referenced this pull request Jul 13, 2026
The Release workflow runs on every push to main. On a merge with no pending
changeset (Dependabot, docs, chore), changesets/action still ran `publish`,
which tried to re-publish the current version. Since it's already on npm,
changesets 2.31.0 crashed parsing npm's "already published" response instead of
no-opping — red-X-ing every routine merge (e.g. run #27 from the #39 merge).

Guard the step: only run changesets/action when a changeset is pending or the
local version isn't the one published on npm. Routine merges now skip it; the
real release paths (open the version PR / publish the bumped version) are
unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants