Skip to content

security: extend cooldown exempt list with prime-pydantic-config#76

Open
burnpiro wants to merge 1 commit into
mainfrom
security/cooldown-7d
Open

security: extend cooldown exempt list with prime-pydantic-config#76
burnpiro wants to merge 1 commit into
mainfrom
security/cooldown-7d

Conversation

@burnpiro
Copy link
Copy Markdown

@burnpiro burnpiro commented May 29, 2026

What

Reformats the existing exclude-newer-package inline table into a section and adds prime-pydantic-config (the only first-party PI package in renderers' uv tree closure besides renderers itself).

[tool.uv.exclude-newer-package]
fastokens             = false  # (existing — fastokens 0.2.0 carve-out)
prime-pydantic-config = false  # ← new

Why

Part 1 of a 3-phase supply-chain hardening rolling out across PrimeIntellect repos. renderers already had the cooldown — this PR just completes the canonical first-party exempt set for packages this project actually depends on.

Notes

  • Lock not regenerated due to a pre-existing hatch-vcs issue with the local checkout's tag state (0.1.8.dev37 can't be bumped). The pyproject change is correct and will apply on the next successful uv lock after the tag situation is sorted.
  • Trimmed: only packages in renderers' actual closure are listed.

🤖 Generated with Claude Code


Note

Medium Risk
Narrows the 7-day supply-chain cooldown for a runtime dependency (prime-pydantic-config); intentional first-party carve-out but weakens the gate for that package.

Overview
Tightens uv supply-chain policy in pyproject.toml by pinning required-version = ">=0.11.1" so the "7 days" exclude-newer cooldown is parsed correctly (older uv can skip the policy silently).

The inline exclude-newer-package map is moved to a dedicated [tool.uv.exclude-newer-package] section. prime-pydantic-config = false is added next to the existing fastokens exemption so first-party PI packages in this repo’s dependency tree can resolve without the 7-day gate; comments document why each package is exempt.

Reviewed by Cursor Bugbot for commit 9f3b24c. Bugbot is set up for automated code reviews on this repo. Configure here.

Note

Exempt prime-pydantic-config from the 7-day uv dependency cooldown

Adds prime-pydantic-config to the tool.uv.exclude-newer-package exemptions in pyproject.toml, alongside the existing exemption. Also sets a minimum uv version requirement of >=0.11.1 to support the per-package exemption syntax.

Macroscope summarized 9f3b24c.

macroscopeapp[bot]
macroscopeapp Bot previously approved these changes May 29, 2026
@macroscopeapp
Copy link
Copy Markdown

macroscopeapp Bot commented May 29, 2026

Approvability

Verdict: Approved

This PR modifies build tooling configuration (uv package manager settings) to add a first-party package to the dependency cooldown exempt list and enforce a minimum uv version for correct parsing. No runtime code is affected - changes only impact dependency resolution during builds.

You can customize Macroscope's approvability policy. Learn more.

renderers already had exclude-newer = "7 days" with a per-package
exemption for fastokens. This PR splits the inline table into a
[tool.uv.exclude-newer-package] section and adds the only other
PrimeIntellect-published package in renderers' dep closure:
prime-pydantic-config.

Only packages in this project's `uv tree` are exempted — the resolver
ignores entries for packages it never sees.

Pins `required-version = ">=0.11.1"` so older uvs fail loudly instead
of silently parsing "7 days" as an RFC 3339 date and proceeding
*without* the cooldown — see uv#17908.

Part 1 of 3 in a coordinated supply-chain hardening across PI repos.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants