From aec6f5c2d580bb325856dfc726e7b5f94126d897 Mon Sep 17 00:00:00 2001 From: Noah Schatz Date: Fri, 25 Sep 2026 20:20:24 +0000 Subject: [PATCH] Exempt @cosyte packages from the 24-hour release-age floor OPERATOR: "I need every single package on v0.1.x and published. I need extensive marketing material to get cosyte off the ground and start bringing in business." and "Nothing is off limits. Create a marketing repo as needed to get cosyte MOVING!" Among options put to them for the v0.1 launch, the operator chose to exempt @cosyte/* from the 24-hour release-age floor and keep it for every third-party package. Claude-Session: https://claude.ai/code/session_01U24bnHKNxQWMxmfN7ny7w9 --- pnpm-workspace.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml index 2306aa3..c6672da 100644 --- a/pnpm-workspace.yaml +++ b/pnpm-workspace.yaml @@ -28,7 +28,11 @@ # package repo. pnpm's own rationale for the number: "Since malware is usually # detected quickly, delaying updates by 24 hours will most likely prevent you # from installing a bad version" (https://pnpm.io/supply-chain-security). +# @cosyte is exempt by operator decision; every third-party package keeps the floor. minimumReleaseAge: 1440 +minimumReleaseAgeExclude: + # reason: first-party @cosyte package, exempt from the floor by operator decision + - "@cosyte/*" # Fail the install when a package's trust evidence is weaker than that of an # earlier-published version of the same package (a trusted publisher that