Repository navigation
Commit 89718f5
authored
Release 3.2.2: require agentscore-py 2.8.1 for its certifi floor (#166)
## Summary
Release 3.2.2. This raises the `agentscore-py` floor from 2.8.0 to
2.8.1.
agentscore-py 2.8.1 requires `certifi>=2026.10.19`. Older certifi
releases trust emSign roots whose intermediate CA keys were compromised
(GHSA-6q48-6c7w-9gw2). With the new floor, any install of
agentscore-commerce 3.2.2 resolves a certifi that does not trust those
roots. The floor lives in agentscore-py, so this package does not repeat
it.
In the lockfile, agentscore-py moves to 2.8.1 and certifi moves from
2026.10.18 to 2026.10.19.
Worked with Varun.
## Type of change
- [x] Bug fix (no breaking change)
- [ ] New feature (no breaking change)
- [ ] Breaking change (existing callers must update)
- [ ] Docs, tests, or internal maintenance only
## Public API
Unchanged. The one changed requirement is `agentscore-py>=2.8.1`.
## Test plan
- `uv sync --frozen --all-extras --all-groups`, then:
- `uv run pytest`: 1674 passed, 4 skipped.
- `uv run ruff check .` and `uv run ruff format --check .`: clean.
- `uv run ty check`: clean.
- `uv run vulture . --min-confidence 80 --exclude .venv`: clean.
- `osv-scanner` on `uv.lock`: no issues found.
## Checklist
- [ ] Tests cover the new behavior, and the suite passes locally (a
dependency floor adds no behavior to test; the existing suite passes)
- [x] Lint, format, and type checks pass
- [ ] Docs and README examples updated if the public surface changed
(the public surface did not change)
- [x] No secrets, credentials, or personal data in the diff or the tests1 parent 5c8672c commit 89718f5
2 files changed
Lines changed: 11 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
| 7 | + | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
15 | | - | |
| 15 | + | |
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments