Repository navigation
Conversation
- turbo orchestrates builds in dependency order with a cache - cli depends on api/get via workspace:^ and builds with plain tsc - husky commit-msg hook and PR/push commitlint checks - dependabot commits use chore(deps) prefix Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- release PR is opened on releasable conventional commits; merging releases - api/get publish to npm when their version is missing from npm, then tag - cli publishes after libs, builds pkg binaries, uploads to its GitHub Release - replaces the tag-push workflow Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
dev failed on a clean checkout because api/get dist did not exist yet. Co-Authored-By: Claude Sonnet 5.5 <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.
Implements #52.
Also makes #31 redundant: the "Get Changes" step is gone, and release-please generates the changelog and release notes.
Changes
Tooling and CI
buildin dependency order, with a cache.clibuilds with plaintscand depends onapi/getviaworkspace:^, so release PRs do not invalidateyarn.lock.commit-msghook with commitlint (conventional commits, optional scope fromapi|get|cli|deps|ci|release|repo).ci.yml: lints PR titles and pushes tomaster, and builds with a.turbocache.dependabot.yml:chore(deps)commit prefix..deploy/tag.jsand thetagscript; recommended Yarn.gitignore; stop tracking.yarn/install-state.gz.devdepends on^buildsoyarn devworks on a clean checkout.Releases
bootstrap-shais81e65c8.release.ymlreplaces the tag-push workflow:api/getpublish to npm when their version is missing from npm, then get tagged;clipublishes afterwards, builds thepkgbinaries, and uploads them to its GitHub Release.Before merging
RELEASE_PLEASE_TOKENsecret (PAT or GitHub App token)release.ymlnode-workspaceleavesworkspace:^intact (yarn install --immutablepasses on the release PR); then a full end-to-end run on a test branch with npm publishing disabledbootstrap-shaifmastermoves before mergeThe first commit (tooling + CI) has no release impact; the second (release-please) is the cutover and could be split out if V1–V3 are not done yet.
🤖 Generated with Claude Code