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
Fixes an annoying release bug, with JSR failing for
inngest
.See https://github.com/inngest/inngest-js/actions/runs/11741974959/job/32711752350
We don't usually require extensions for libraries because we expect packages to also have ESM exports declared in their
package.json
, butnext
does not do this, so we must explicitly use the extension still.Annoyingly, a dry run publish with
jsr
doesn't reveal this. 🙄Checklist
Added a docs PR that references this PRN/A CI fixAdded unit/integration testsN/A CI fix