chore(deps): update dependency write-file-atomic to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
write-file-atomic	^3.0.3 -> ^6.0.0

---

Release Notes

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

v6.0.0

Compare Source

⚠️ BREAKING CHANGES

• write-file-atomic now supports node ^18.17.0 || >=20.5.0

Bug Fixes

• e4db381 #​208 align to npm 10 node engine range (@​hashtagchris)

Chores

• 384ec4c #​208 run template-oss-apply (@​hashtagchris)
• 1a8883d #​206 bump @​npmcli/eslint-config from 4.0.5 to 5.0.0 (@​dependabot[bot])
• 73bddd9 #​194 linting: no-unused-vars (@​lukekarrys)
• 4a16903 #​194 bump @​npmcli/template-oss to 4.22.0 (@​lukekarrys)
• 944e6c2 #​207 postinstall for dependabot template-oss PR (@​hashtagchris)
• c2c17b7 #​207 bump @​npmcli/template-oss from 4.23.1 to 4.23.3 (@​dependabot[bot])

v5.0.1

Compare Source

Dependencies

• a0daf64 #​157 bump signal-exit from 3.0.7 to 4.0.1 (#​157)

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

• 5506c07 #​122 postinstall for dependabot template-oss PR (@​lukekarrys)

v4.0.2

Compare Source

Bug Fixes

• linting (#​111) (c8ef004)

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

• move to template-oss (266833d)

dependencies

• typedarray-to-buffer@4.0.0 (f36ff4f)

Documentation

• readme: clean up API/usage syntax (#​90) (22c6990)

---

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 265ms
➤ YN0000: ┌ Fetch step
➤ YN0001: │ Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
    at PassThrough.onclose (node:internal/streams/end-of-stream:154:30)
    at PassThrough.emit (node:events:519:28)
    at emitCloseNT (node:internal/streams/destroy:147:10)
    at process.processTicksAndRejections (node:internal/process/task_queues:81:21)
➤ YN0001: │ Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
    at PassThrough.onclose (node:internal/streams/end-of-stream:154:30)
    at PassThrough.emit (node:events:519:28)
    at emitCloseNT (node:internal/streams/destroy:147:10)
    at process.processTicksAndRejections (node:internal/process/task_queues:81:21)
➤ YN0013: │ No packages were cached - 2 packages had to be fetched
➤ YN0000: └ Completed in 0s 312ms
➤ YN0000: Failed with errors in 0s 579ms