Release: publish tmp/release/dist folder when releasing #5681
+4
���1
Conversation
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
mgol
approved these changes
Aug 4, 2025
Member
|
LGTM once #5682 lands and this PR is rebased. |
Member
|
We'll also need to backport to |
Member
|
@timmywil you can rebase now. |
Member
Author
indeed, that was my plan |
mgol
added a commit
to mgol/jquery
that referenced
this pull request
Aug 6, 2025
PR jquerygh-5681 specified the `tmp/release/dist` folder as `publishPath` so that `npm publish` is done from the dist repo, not the source one. However, `npm publish` is invoked by release-it before the post-release phase, at which stage the dist repo is not updated with the new release yet. Instead, do the `npm publish` manually in the post-release stage, just after the dist repo is updated & changes are pushed.
mgol
added a commit
to mgol/jquery
that referenced
this pull request
Aug 11, 2025
PR jquerygh-5681 specified the `tmp/release/dist` folder as `publishPath` so that `npm publish` is done from the dist repo, not the source one. However, `npm publish` is invoked by release-it before the post-release phase, at which stage the dist repo is not updated with the new release yet. Instead, do the `npm publish` manually in the post-release stage, just after the dist repo is updated & changes are pushed.
mgol
added a commit
that referenced
this pull request
Aug 11, 2025
PR gh-5681 specified the `tmp/release/dist` folder as `publishPath` so that `npm publish` is done from the dist repo, not the source one. However, `npm publish` is invoked by release-it before the post-release phase, at which stage the dist repo is not updated with the new release yet. Instead, do the `npm publish` manually in the post-release stage, just after the dist repo is updated & changes are pushed. Closes gh-5690
mgol
added a commit
that referenced
this pull request
Aug 11, 2025
PR gh-5681 specified the `tmp/release/dist` folder as `publishPath` so that `npm publish` is done from the dist repo, not the source one. However, `npm publish` is invoked by release-it before the post-release phase, at which stage the dist repo is not updated with the new release yet. Instead, do the `npm publish` manually in the post-release stage, just after the dist repo is updated & changes are pushed. Closes gh-5690 (cherry picked from commit ff1f0ea)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Also update AUTHORS.txt in preparation for rc.1.
Fixes #5658
Checklist