Repository navigation
chore: release 0.4.0 - #115
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.4.0: module and class bodies analysed (#113), justified advisory entry points with conditions and evidence levels (#109), version range unions (#112),
ProjectPlugin.refine(#106), single-file plugin modules insys.modules(#105).pyproject.toml,coretrace_python.__version__, the release test and the report example of the usage guide.CHANGELOG.md:Unreleaseddated as 0.4.0; the feat: justify advisory entry points, keep their conditions and record evidence levels #109 and feat: accept a union of version ranges in a specifier #112 entries gain their references like the rest of the file.Full suite 928 passed; ruff and mypy clean. Tag
v0.4.0after merge to publish.