Repository navigation
Exempt @cosyte packages from the 24-hour release-age floor - #91
Merged
Merged
Conversation
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
NSchatz
enabled auto-merge (squash)
September 25, 2026 20:21
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
1 participant
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.
Adds
minimumReleaseAgeExcludetopnpm-workspace.yamlso our own@cosytepackages are not held back by the 24-hour release-age floor. Every third-party package keeps the 1440-minute floor, andtrustPolicyis unchanged."@cosyte/*".packageManagerpins pnpm 10.34.5, and pnpm reads patterns inminimumReleaseAgeExcludefrom 10.17.0 ("You may also use patterns. For instance, allow all packages from a scope: @babel/*", https://pnpm.io/settings/dependency-resolution).@cosyteis exempt by operator decision and every third-party package keeps the floor. Each entry carries a# reason:comment on the line directly above it, the rule config's install-hardening gate enforces.Why
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.
Checked locally
npx -y pnpm@10.34.5 install --frozen-lockfile: exit 0, lockfile unchanged.parseYamlSubset(the parser drift-check grades this file with), every entry has a reason underexemptionReasons, and drift-check's installHardening group matches.prettier --check pnpm-workspace.yaml: clean.No changeset: nothing here reaches the published tarball.
https://claude.ai/code/session_01U24bnHKNxQWMxmfN7ny7w9