Skip to content

Commit 2c7e07b

Browse files
authored
Merge pull request #120 from CoreTrace/release/0.5.0
chore: release 0.5.0
2 parents 69f5423 + 438dfb0 commit 2c7e07b

5 files changed

Lines changed: 9 additions & 9 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# Changelog
22

3-
## Unreleased
3+
## 0.5.0 (2026-09-24)
4+
5+
### Dependencies
6+
7+
- Argument conditions of advisory entry points are decided at each call, with a `position` for positional arguments and a `default` for absent ones: a call meeting them is reported with `conditions_met`, a call passing another known value does not reach the vulnerability and is listed in the requirement's `ruled_out`, and a call the analyzer cannot decide leaves them pending review (#110).
48

59
### Plugins
610

711
- `ProjectContext.functions(module)` gives project plugins every function of a module as its call graph names it, with its span and the label of the entry point it is (`http` for a route, `argv` for a command), decided by the taint engine's own rule; modules served from the cache keep them, and the cache format is bumped (#116).
812
- Call sites and external calls record what each argument denotes — a symbol, a constant as Python writes it, or nothing known — in an `Arguments` record: `CallSite.arguments` (formerly the argument counts), `ExternalCall.arguments`, and `TaintFlow.sink_arguments` for the sink call of a flow, through callees in other modules too (#110).
913

10-
### Dependencies
11-
12-
- Argument conditions of advisory entry points are decided at each call, with a `position` for positional arguments and a `default` for absent ones: a call meeting them is reported with `conditions_met`, a call passing another known value does not reach the vulnerability and is listed in the requirement's `ruled_out`, and a call the analyzer cannot decide leaves them pending review (#110).
13-
1414
## 0.4.0 (2026-09-24)
1515

1616
### Analysis

‎docs/usage.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ the directory of the checked file; a path outside it is printed as it is.
201201
```json
202202
{
203203
"schema_version": 1,
204-
"tool": {"name": "coretrace-python-analyzer", "version": "0.4.0"},
204+
"tool": {"name": "coretrace-python-analyzer", "version": "0.5.0"},
205205
"root": "/home/me/project",
206206
"findings": [
207207
{

‎pyproject.toml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
44

55
[project]
66
name = "coretrace-python-analyzer"
7-
version = "0.4.0"
7+
version = "0.5.0"
88
description = "Static security analysis infrastructure for Python code"
99
readme = "README.md"
1010
requires-python = ">=3.11"

‎src/coretrace_python/__init__.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
"""CoreTrace's Python static analysis frontend."""
22

3-
__version__ = "0.4.0"
3+
__version__ = "0.5.0"
44

‎tests/test_release.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ def require_changelog() -> None:
3030
def test_the_version_is_declared_once_and_mirrored() -> None:
3131
project = tomllib.loads((REPO / "pyproject.toml").read_text(encoding="utf-8"))["project"]
3232

33-
assert project["version"] == coretrace_python.__version__ == "0.4.0"
33+
assert project["version"] == coretrace_python.__version__ == "0.5.0"
3434

3535

3636
def test_the_changelog_starts_with_the_current_version() -> None:

0 commit comments

Comments
 (0)