chore: remove stale cli-bundle/ directory#9
Merged
Conversation
cli-bundle/ is a leftover from the pre-esbuild bundle layout (last updated in the v0.0.4/v0.1.0 releases, Oct 2025). The action runs from dist/index.js (see action.yml) and nothing references cli-bundle/, so it is dead weight. Drop it and the AGENTS.md references to it.
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
cli-bundle/is a stale ~40-file directory from the pre-esbuild bundle layout (last touched in the v0.0.4 / v0.1.0 releases, Oct 2025). The action runs fromdist/index.js(action.yml) and nothing in the repo referencescli-bundle/— it is dead weight.It also actively breaks releases: the monorepo mirror sync deletes any path outside the release-artifact set, so every generated release PR carries a
cli-bundle/deletion that failsvalidate-release-pr. Removing it frommainresolves that.This drops
cli-bundle/and the two staleAGENTS.mdreferences to it.Note on CI
validate-release-pris expected to fail here — its maintenance-scope step only permits.github/*changes, and this is a one-time content cleanup. It is an advisory (non-required) check.