chore(deps): bump tempfile from 3.13.0 to 3.20.0

[dependabot]

Bumps tempfile from 3.13.0 to 3.20.0.

Changelog

Sourced from tempfile's changelog.

3.20.0

This release mostly unifies the behavior/capabilities around "keeping" temporary files:

• Rename Builder::keep(bool) (via deprecation) to Builder::disable_cleanup(bool) to make it clear that behaves differently from NamedTempFile::keep(). The former disables automatic cleanup while the latter consumes the NamedTempFile object entirely and unsets the "temporary file" attribute (on Windows).
• Rename TempDir::into_path (via deprecation) to TempDir::keep to mirror NamedTempFile::keep.
• Add TempDir::disable_cleanup, NamedTempFile::disable_cleanup, and TempPath::disable_cleanup making it possible to disable automatic cleanup in-place after creating a temporary file/directory (equivalent to calling Builder::disable_cleanup before creating the file/directory).

Additionally, it adds a few spooled temporary file features:

• Add SpooledTempFile::into_file for turning a SpooledTempFile into a regular unnamed temporary file, writing it to the backing storage ("rolling" it) if it was still stored in-memory.
• Add spooled_tempfile_in and SpooledTempFile::new_in methods for creating spooled temporary files in a specific directory. This makes it possible to choose the backing device for your spooled temporary file which is rather important on Linux where the default temporary directory is likely backed by memory (defeating the entire point of having a spooled temporary file).

Finally, this release improves documentation, especially the top-level documentation explaining which temporary file type to use.

BREAKING for those with deny(warnings):

• Builder::keep deprecated in favor of Builder::disable_cleanup.
• TempDir::into_path is deprecated in favor of TempDir::keep.

BREAKING:

3.19.1

• Don't unlink temporary files immediately on Windows (fixes #339). Unfortunately, this seemed to corrupt the file object (possibly a Windows kernel bug) in rare cases and isn't strictly speaking necessary.

3.19.0

• Remove direct dependency on cfg-if. It's still in the tree, but we didn't really need to use it in this crate.
• Add an unstable feature (unstable-windows-keep-open-tempfile) to test a potential fix to #339.

3.18.0

• Update rustix to 1.0.0.
• Make NamedTempFile::persist_noclobber atomic on Apple operating systems. It's now atomic on MacOS, Windows, and Linux (depending on the OS version and filesystem used).

3.17.1

• Fix build with windows-sys 0.52. Unfortunately, we have no CI for older windows-sys versions at the moment...

3.17.0

• Make sure to use absolute paths in when creating unnamed temporary files (avoids a small race in the "immediate unlink" logic) and in Builder::make_in (when creating temporary files of arbitrary types).
• Prevent a theoretical crash that could (maybe) happen when a temporary file is created from a drop function run in a TLS destructor. Nobody has actually reported a case of this happening in practice and I have been unable to create this scenario in a test.
• When reseeding with getrandom, use platform (e.g., CPU) specific randomness sources where possible.
• Clarify some documentation.
• Unlink unnamed temporary files on windows immediately when possible instead of waiting for the handle to be closed. We open files with "Unix" semantics, so this is generally possible.

3.16.0

... (truncated)

Commits

• 99ffea6 chore: release v3.20.0 (#358)
• bd2b267 feat: make it possible to disable cleanup in-place after creation (#355)
• 3b30099 ci: really check docs for warnings (#357)
• f701f52 ci: check docs (#356)
• d34afe9 doc: improve SpooledData documentation
• 6deb42e doc: make it easier to pick the correct tempfile constructor/type
• e284782 feat: allow creating spooled temporary files in a specific directory (#353)
• 07edc31 feat: implement SpooledTempFile::into_file (#352)
• b122355 fix: add must_use attribute to TempDir::keep (#351)
• cbd1e97 feat: rename TempDir::into_path to TempDir::keep (#349)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jeertmans]

Superseded by #117

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.