Skip to content

Commit 10216b3

Browse files
authored
chore: v1.4.19 changelog bump
Signed-off-by: GitHub <[email protected]>
1 parent ffa1df6 commit 10216b3

File tree

1 file changed

+79
-0
lines changed

1 file changed

+79
-0
lines changed

CHANGELOG.md

+79
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,82 @@
1+
<a name="v1.4.19"></a>
2+
## [v1.4.19] - 2023-03-20
3+
[v1.4.19]: https://github.com/quay/claircore/compare/v1.4.18...v1.4.19
4+
5+
- Better jar names
6+
<details>
7+
The heuristic for extracting package names from jars has been improved
8+
and may yield different results.
9+
</details>
10+
11+
- URLs are now included in the prose documentation
12+
<details>
13+
Previous, changes to URLs needed to be copied into the prose documentation;
14+
this means the documentation was almost always out of sync.
15+
There's now a tool to process comment directives and slipstream the URLs into th
16+
e documentation in the build step.
17+
Contributors should see the `docs/injecturls.go` file for information on how to
18+
use the system in code.
19+
</details>
20+
21+
- Dpkg indexing honors the "Status" field
22+
<details>
23+
Previously, a dpkg-installed package that kept around dpkg-tracked files
24+
after removal would be reported as installed.
25+
</details>
26+
27+
- Improved indexing of python packages
28+
<details>
29+
The python package indexer now detects some package managers and omits
30+
indexing the parts of the filesystem that those package managers would
31+
place python packages.
32+
</details>
33+
34+
- Handling of "pep440" versions has changed
35+
<details>
36+
Previously, versions of type "pep440" were inadvertently handled by two
37+
different packages -- one was used for validation, another for
38+
comparisons. Claircore now uses a single package. There should be no
39+
noticeable change in the behavior of python indexing or matching, so
40+
please file bugs if there are regressions.
41+
</details>
42+
43+
- Update required go version to 1.20
44+
<details>
45+
This is needed to fix [go issue 33121](https://go.dev/issue/33121),
46+
which was indirectly triggered by the `gobin` indexer.
47+
</details>
48+
49+
- Distroless container support
50+
<details>
51+
Claircore's `dpkg` indexer now supports the "distroless" scheme, where
52+
the `dpkg` status database is split across multiple files.
53+
</details>
54+
55+
- RPM is removed as a dependency
56+
<details>
57+
Claircore no longer requires `rpm`. Previously, `rpm` was executed as a
58+
subprocess to examine rpm's BerkeleyDB-based databases. This required
59+
extra disk space, extra dependencies, and had the potential to leak
60+
resources. Now, claircore implements just enough knowledge of the
61+
BerkeleyDB hash database format to be able to extract headers that it
62+
already had the means to interpret. Users of claircore should also be
63+
able run without zombie handling, as claircore no longer spawns
64+
subprocesses.
65+
</details>
66+
67+
- The python indexer consults INSTALLER metadata
68+
<details>
69+
The indexer now ignores installers that it knows beforehand is handled
70+
elsewhere.
71+
</details>
72+
73+
- rpm: extract a minimal file set for bdb-based databases
74+
<details>
75+
This should reduce runtime and disk resources when the `rpm` indexer
76+
decides that it needs to invoke `rpm` to analyze packages installed in a
77+
layer.
78+
</details>
79+
180
<a name="v1.4.18"></a>
281
## [v1.4.18] - 2023-01-27
382
[v1.4.18]: https://github.com/quay/claircore/compare/v1.4.17...v1.4.18

0 commit comments

Comments
 (0)