Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Bump to v1.46.0

Add ExplicitCommit option to provide calling code the ability to
preserve original files when an application error occurs, not just
an error that occurs during writing.

Change Close() impl to safely handle redundant calls (for defer
usage safety)

Signed-off-by: Jason T. Greene <jason.greene@redhat.com>

Bumps [github.com/klauspost/compress](https://github.com/klauspost/compress) from 1.16.3 to 1.16.4.
- [Release notes](https://github.com/klauspost/compress/releases)
- [Changelog](https://github.com/klauspost/compress/blob/master/.goreleaser.yml)
- [Commits](klauspost/compress@v1.16.3...v1.16.4)

---
updated-dependencies:
- dependency-name: github.com/klauspost/compress
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: Renovate Bot <bot@renovateapp.com>

chore(deps): update dependency containers/automation_images to v20230405

….com/klauspost/compress-1.16.4

build(deps): bump github.com/klauspost/compress from 1.16.3 to 1.16.4

Improve AtomicFileWriter's support for Win and Mac

We previously started "pulling up" images when we changed their names,
and started denying the presence of images in read-only stores which
shared their ID with an image in the read-write store, so that it would
be possible to "remove" names from an image in read-only storage.  We
forgot about the Flags field, so start pulling that up, too.

Do all of the above when we're asked to create an image, since denying
the presence of images with the same ID in read-only stores would
prevent us from finding the image by any of the names that it "had" just
a moment before we created the new record.

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>

"pull up" images when creating them, too

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>