You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
--timing file changes:
When run with the --timing flag, npm now writes timing data to a
file alongside the debug log data, respecting the logs-dir option and
falling back to <CACHE>/_logs/ dir, instead of directly inside the
cache directory.
The timing file data is no longer newline delimited JSON, and instead
each run will create a uniquely named <ID>-timing.json file, with the <ID> portion being the same as the debug log.
Finally, the data inside the file now has three top level keys, metadata, timers, and unfinishedTimers` instead of everything being
a top level key.
npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.
node . run lint-all
node . run test-all
node scripts/git-dirty.js
3. Check CI status
gh pr checks --watch
4. Publish workspaces
Note:
If we are currently publishing prereleases, make sure to publish with the prerelease tag.
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.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
release-please--branches--latest
branch
6 times, most recently
from
🤖 I have created a release beep boop
9.0.0-pre.3
9.0.0-pre.3 (2022-09-30)
npm packnow follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.--timingfile changes:--timingflag,npmnow writes timing data to afile alongside the debug log data, respecting the
logs-diroption andfalling back to
<CACHE>/_logs/dir, instead of directly inside thecache directory.
each run will create a uniquely named
<ID>-timing.jsonfile, with the<ID>portion being the same as the debug log.metadata,timers, andunfinishedTimers` instead of everything beinga top level key.
Features
3ae796dimplement newnpm-packlistbehavior (@lukekarrys)e64d69a#5581 write eresolve error files to the logs directory (@lukekarrys)3445da0timings are now written alongside debug log files (@lukekarrys)Documentation
f0e7584#5601 update docs/logging for new --access default (@wraithgar)Dependencies
bc21552#5603npm-package-arg@9.1.2@npmcli/arborist@6.0.0-pre.3libnpmdiff@5.0.0-pre.1libnpmexec@5.0.0-pre.3libnpmfund@4.0.0-pre.3libnpmpack@5.0.0-pre.1libnpmpublish@7.0.0-pre.1arborist: 6.0.0-pre.3
6.0.0-pre.3 (2022-09-30)
npm packnow follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.Features
3ae796dimplement newnpm-packlistbehavior (@lukekarrys)libnpmdiff: 5.0.0-pre.1
5.0.0-pre.1 (2022-09-30)
npm packnow follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.Features
3ae796dimplement newnpm-packlistbehavior (@lukekarrys)Dependencies
@npmcli/arborist@6.0.0-pre.3libnpmexec: 5.0.0-pre.3
5.0.0-pre.3 (2022-09-30)
npm packnow follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.Features
3ae796dimplement newnpm-packlistbehavior (@lukekarrys)Dependencies
@npmcli/arborist@6.0.0-pre.3libnpmfund: 4.0.0-pre.3
4.0.0-pre.3 (2022-09-30)
Dependencies
@npmcli/arborist@6.0.0-pre.3libnpmpack: 5.0.0-pre.1
5.0.0-pre.1 (2022-09-30)
npm packnow follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.Features
3ae796dimplement newnpm-packlistbehavior (@lukekarrys)Dependencies
@npmcli/arborist@6.0.0-pre.3libnpmpublish: 7.0.0-pre.1
7.0.0-pre.1 (2022-09-30)
accessis nowpublicFeatures
525654edefault access topublic(@wraithgar)Documentation
f0e7584#5601 update docs/logging for new --access default (@wraithgar)This PR was generated with Release Please. See documentation.