Update uuid 9.0.0 → 9.0.1 (patch) #3018
Merged
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ uuid (9.0.0 → 9.0.1) · Repo · Changelog
Release Notes
9.0.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 18 commits:
chore(release): 9.0.1
chore: add node@12 back to CI, update readme (#733)
ci: update node versions for cI (#732)
test: remove missing getRandomValues test (#709)
chore: adapt bundlewatch config to new main branch name (#705)
chore: run npm audit fix for json5 (#704)
ci: run browser tests on pull_request_target (#703)
chore: minor typos in non-code areas (#702)
chore: upgrade and fix the stale-issues workflow (#699)
chore: add SECURITY.md, fixes #696 (#697)
Replace broken image in README file (#695)
docs: add note about `cypto.randomUUID()` (#686)
chore: enable stale-exempt label (#679)
perf: remove superfluous call to toLowerCase (#677)
docs: typo (#667)
test: restore ctavan to funding
test: remove @ctavan (temporarily)
chore: add FUNDING.yml, package.json#funding, fixes #384 (#659)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands