This repository was archived by the owner on Aug 8, 2026. It is now read-only.
Wind down the package ahead of deprecation - #1707
Merged
Merged
Conversation
Every fleet repo now releases through the tanem/release-action composite action, so nothing depends on this package any more. This is the repo-side half of retiring it; the npm deprecation and the archive follow. The weekly release cron goes, so no release can fire from here again. The release npm script goes with it — the workflow was its only caller, and left in place it would regenerate the CHANGELOG.md this commit freezes. CHANGELOG.md is frozen at v8.0.8 with a pointer to the README, and the README shrinks to a deprecation pointer at the action. Both stay clear of asserting the npm deprecation and the archive as done, since those are owner steps that land after this commit. AUTHORS and its generation go with it. The file itself, the authors command and module, its keywords, and the step in release() that regenerated the file on every release are all removed — the action has no successor for any of it, by design. .mailmap stays: git honours it natively for shortlog and blame, so it keeps author names normalised in the archived history. The changelog command stays too — it is what the action replaces rather than drops.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Every fleet repo now releases through the tanem/release-action composite action, so nothing depends on this package any more. This is the repo-side half of retiring it — the npm deprecation and the archive are owner steps that follow this merge, in that order.
The weekly release cron goes, so no release can fire from here again. The
releasenpm script goes with it: the workflow was its only caller, and left in place it would regenerate the CHANGELOG.md this PR freezes.CHANGELOG.md is frozen at v8.0.8 with a pointer to the README, and the README shrinks to a deprecation pointer at the action. Both stay clear of asserting the npm deprecation and the archive as already done, since neither has happened at merge time.
AUTHORS and its generation go too — the file, the
authorscommand and module, its keywords, and the step inrelease()that regenerated the file on every release. The action has no successor for any of it, by design..mailmapstays, because git honours it natively for shortlog and blame and it keeps author names normalised in the archived history. Thechangelogcommand stays as well: it is what the action replaces rather than drops.npm testis green — typecheck, format, lint, build, and 5 tests across both jest configs.