Repository navigation
ci(release): bump @basou/cli alongside @basou/core in the docs-bump PR - #39
Merged
Merged
Conversation
The update-docs-site job now pins @basou/cli to the released version too, so basou-site regenerates the CLI command reference (which imports @basou/cli/program) on every release, not just the @basou/core version-coupled regions. Updates the PR branch name, title, commit message, and body to name both packages. Co-Authored-By: Claude Opus 4.8 (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
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.
The release pipeline's
update-docs-sitejob pinned only@basou/corein basou-site. Now that the docs site generates the CLI command reference by importing@basou/cli/program, the job must pin@basou/clitoo, or the reference would drift from the released binary (andgen:docswould resolve a stale@basou/cli).Change
@basou/cli@${version}to thepnpm add -Eline so both packages are pinned to the just-published version (lockstep).bump/basou-core-*→bump/basou-*), commit message, title, and body to name both packages.No GitHub Action versions change (SHA pins untouched); this is shell / YAML text only. The
add-pathsallowlist already coverspackage.json/pnpm-lock.yaml/src/content/docs/**, so the regenerated reference rides along with no allowlist change.Pairs with basou-site#6 (which lands the generated reference page and the
@basou/clidependency).