Skip to content

docs(pnpm-policy): stop publishing our account topology - #115

Merged
pyramation merged 1 commit into
mainfrom
docs/pnpm-policy-readme
Aug 6, 2026
Merged

docs(pnpm-policy): stop publishing our account topology#115
pyramation merged 1 commit into
mainfrom
docs/pnpm-policy-readme

Conversation

@pyramation

Copy link
Copy Markdown
Contributor

The pnpm-policy README described our package count as sitting "behind one maintainer account". That is a statement about how our publishing is structured, on the public README of a tool whose entire subject is supply-chain risk — it names the single thing worth compromising.

Two edits, both in packages/pnpm-policy/README.md:

-At Constructive that is 1104 published packages behind one maintainer account, fetched in 5 requests…
+At Constructive that is over 1100 published packages, fetched in 5 requests…

-…are written out — 1104 published packages becomes the ~85 that appear in this repo.
+…are written out — over 1100 published packages becomes the ~85 that appear in this repo.

The number is what carries the argument — a bare wait would make every repo un-installable after each of our own releases. How many accounts sit behind it does not.

The exact count goes too, for a smaller reason: it is precise enough to track over time and adds nothing the rounded figure doesn't.

maintainers stays everywhere else in the README — it is the config key and the concept, and the docs need it to explain what the setting does. What is removed is only the description of our own arrangement. I checked the rest of the repo, including packages/constructive-pnpm-policy, for the same phrasing and the exact count; there are no other occurrences.

Docs only — no code, no behaviour change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CEswUi4ANuB58rva48aHge

The README stated our package count "behind one maintainer account".
That is a detail about how our publishing is structured, on a public
README for a tool whose whole subject is supply-chain risk — it points
at the single thing worth compromising.

Says "over 1100 published packages" instead. The number carries the
point (a bare wait would stall on our own releases constantly); how many
accounts sit behind it does not.

The exact count is dropped in both places for the same reason: it is
precise enough to track over time and adds nothing to the explanation.

`maintainers` stays throughout as the config key and the concept — the
README needs it to explain what the setting does. What is removed is the
statement about our own arrangement.
@pyramation
pyramation merged commit 6196d9e into main Aug 6, 2026
59 checks passed
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.

1 participant