Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency write-file-atomic to v5 #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
write-file-atomic ^3.0.3 -> ^5.0.0 age adoption passing confidence

Release Notes

npm/write-file-atomic (write-file-atomic)

v5.0.1

Compare Source

Dependencies

v5.0.0

Compare Source

⚠️ BREAKING CHANGES
  • write-file-atomic is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0
Features

v4.0.2

Compare Source

Bug Fixes
4.0.1 (2022-02-09)
Bug Fixes
  • remove dupl check for typed arrays (#​96) (81a296d)
  • remove is-typedarray and typedarray-to-buffer (625526e)
Dependencies
  • update signal-exit requirement from ^3.0.2 to ^3.0.7 (0b3ffdb)

v4.0.1

Compare Source

v4.0.0

Compare Source

⚠ BREAKING CHANGES
  • This drops support for node10 and non-LTS versions of node12 and node14
Bug Fixes
dependencies
  • typedarray-to-buffer@4.0.0 (f36ff4f)
Documentation

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

0 participants