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.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
The minimum TLS version is now 1.2.
Previously, servers also allowed 1.1 connections.
Claircore is updated to v1.5.25:
rhcc, rhel: support compression of sideband data
datastore: add "delta" update interface
java: size buffers correctly before use
postgres: remove internal timeouts
integration: make
PGVERSION
a patternAdditionally, the version used is now read from the distributed
manifest, rather than hard-coded versions. Other than occasional network
calls to fetch this manifest, users shouldn't notice any difference.
alpine: add edge support
rpm: support PGP V4 signatures
jsonblob: add a disk buffering step
This makes the API trickier but given that there's a single (known and
intended) user, this should be fine.
tarfs: check a potential interger overflow
The possibility of exploiting this is effectively 0, as it would require
more bytes to represent a sufficiently large integer than is available
in the tar header.
See also: https://github.com/quay/claircore/security/code-scanning/5
gobin: take into account package replacements
all: purge
http.DefaultClient
usageThis change breaks some API in exchange for unifying the
*http.Client
handling. The practical upshot is that it's much easier to control the
network contact surface.
all: share single FS implementation
This change should improve memory usage.
libindex: move to O_TMPFILE fetcher
v4.7.3 - 2024-02-26
Admin
See Also: #1915
Chore
See Also: #1990, #1957, #1942
Config
See Also: #1945