feat!: unify Verzly under a single toolchain release surface#40
Merged
Conversation
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
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.
Reworks the toolchain around a single
verzlyexecutable and oneverzly/toolchainrelease surface.Standalone tools remain available as compatibility entrypoints, but their command logic is now exposed through reusable library entrypoints and routed through the unified
verzlyCLI. Each public tool is also available as a first-class GitHub Action underactions/*, so consuming repositories can use the toolchain directly without wiring multiple distribution repositories.The old distribution-oriented structure is removed, contributor and agent guidance is consolidated into the root README, the action-first workflow is documented, and the repository Clippy failure caused by declaring an item after the test module is fixed.