chore: remove deprecated packages#209
Merged
Merged
Conversation
Removes the source for three packages that were deprecated and republished with `[!CAUTION]` notes + permalink homepages in @vlandoss/biome-config@0.0.9, @vlandoss/localproxy@0.2.3, @vlandoss/starter@0.4.2. The deprecation notice + migration path live on at the tag URLs, so npm consumers still see them on the package page. Note: depends on the deprecate PR being merged AND `npm deprecate` having been run on each package — see the deprecate PR for the post-publish commands. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
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
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.
Summary
Removes the source for the three packages deprecated and republished in #206:
@vlandoss/biome-config(last published:0.0.9)@vlandoss/localproxy(last published:0.2.3)@vlandoss/starter(last published:0.4.2)The deprecation notice + migration paths live on at the tag URLs (
tree/%40vlandoss%2F<pkg>%40<ver>/...) pinned in each package'shomepagefield on npm. Consumers visiting the npm page or installing get the deprecation message and a working link to the README at the moment it was published.npm deprecatehas been applied to all versions (*), so:npm view @vlandoss/biome-config deprecated→ "Deprecated. Use @vlandoss/config/biome instead. ..."npm view @vlandoss/localproxy deprecated→ "Deprecated. Use Portless instead. ..."npm view @vlandoss/starter deprecated→ "Deprecated. Use @vlandoss/vland instead. ..."After this lands
mainis clean and unblocks the upcoming clibuddy refactor (zx → tinyexec).Test plan
pnpm install --frozen-lockfilesucceedspnpm testandpnpm test:typesare green for the remaining packages*.json|*.yml|*.toml|*.ts|*.md, only matches were within the deleted dirs themselves)🤖 Generated with Claude Code