From f4d156d2951d05b8a798f160c70ca8687fcad24c Mon Sep 17 00:00:00 2001 From: Qwynn Marcelle Date: Mon, 17 Aug 2026 13:46:37 -0400 Subject: [PATCH] chore(release): record the published-metadata corrections as a changeset (META-325) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The fixed group's release composition was missing its metadata half. Six changesets covered every code change since 0.4.4, but the manifest corrections that landed with the repository reconstruction and the OSS-polish pass carried none — repository/bugs pointers, the bare canonical homepage, author, two removed keywords, and the rules description. Those fields ship. So do README.md and CHANGELOG.md, both listed in `files`, which were corrected in the same passes with no release note. META-325's acceptance requires every intended public package change to map to an explicit changeset or an explicit no-release-impact decision; this closes the gap on the metadata side. Patch on its own terms. The group is taking a minor this release for reasons recorded in the accompanying changesets, so the number does not move because of this file. --- .changeset/plenty-cooks-repair.md | 41 +++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 .changeset/plenty-cooks-repair.md diff --git a/.changeset/plenty-cooks-repair.md b/.changeset/plenty-cooks-repair.md new file mode 100644 index 0000000..2b22fff --- /dev/null +++ b/.changeset/plenty-cooks-repair.md @@ -0,0 +1,41 @@ +--- +"@workspacejson/rules": patch +"@workspacejson/spec": patch +--- + +Correct the published package metadata to name this repository, and record the +README and changelog corrections that ship inside the tarball. + +Both manifests still described the packages as they were published from the +frozen historical workspace. None of it was reachable: `repository.url` and +`bugs.url` pointed at a repository that no longer exists under that name, so +every "open an issue" and "view source" link on both npm pages led nowhere. + +`repository` now names this repository and carries a `directory` pointer, so npm +resolves each package to its own subtree rather than the monorepo root. `bugs` +follows it. `homepage` is the bare canonical host on both packages, per ADR-005 — +`@workspacejson/rules` additionally pointed at a `/audit/` subpath that predates +the neutral naming and no longer describes what the package is. + +`author` reads `workspacejson contributors` on both, matching the org that now +holds them. + +Two keywords were removed. `agents-audit` named the historical package rather +than these; `aaif` implied a standards-body status this project does not hold. + +`@workspacejson/rules` has a new `description`. The old one described a narrower +package — AGENTS.md hygiene auditing — than the one that actually ships, which +carries the parser, repository scanner, validator and rule engine. + +**Why a metadata-only change gets a changeset at all.** `README.md` and +`CHANGELOG.md` are both listed in `files`, so they are published bytes, not +repository furniture. Both package READMEs claimed to be published from the +historical workspace and loaded their brand assets from a frozen repository; +both changelogs recorded 0.4.4 as unreleased while the registry had already +served it. Those corrections reached consumers with no release note explaining +why the page changed. The manifest fields above are in the same position: they +are part of the published artifact even though no runtime behavior moves. + +Nothing in either package's runtime, types, schema or exports changes. `patch` +is correct on its own terms; the fixed group is taking a `minor` this release +for reasons recorded in the accompanying changesets, and this rides along.