Repository navigation
chore: release 0.10.0 - #151
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release 0.10.0 adds one change, following #149.
Reports name what a result was produced with (Reports: name the plugins and advisory files a result was produced with #149). A directory check lists each plugin it loaded, by manifest name and version, and each advisory file it read, by path, each with the SHA-256 digest of its content. They appear in every format:
tool.components;tool.extensions;metadata.tools.components;tooling, so the document@idchanges with the advisory data.Every finding about an advisory names, in
advisory_source, the plugin (name@version) or advisory file it comes from.A report stays readable by a consumer that ignores the new fields. The cache format does not change.
The curated data needs this release: versioning it (CoreTrace-Entreprise/coretrace-python-analyzer-plugins#34) only lets a result be traced to one dataset once reports name the plugin version.
Changes in this PR
pyproject.toml,coretrace_python.__version__, the release test and the report example of the usage guide.CHANGELOG.md: the Unreleased section is dated as 0.10.0. No entry changed.Verification
pytest: 1110 passed, 2 skipped.pytest -m regressionunder Python 3.12: 19 passed.ruff checkon the tracked files, andmypy: clean.Tag
v0.10.0after merge to publish.