ci: auto-adopt engine releases and tag kai-cli#34
Merged
Conversation
🔍 Kai review |
fatihacet
force-pushed
the
automation/release-please
branch
from
7fc86ba to
3c3ef57
Compare
fatihacet
changed the title
fatihacet
force-pushed
the
automation/release-please
branch
from
3c3ef57 to
fed1486
Compare
On engine-released, go get kai-engine@<version> + go mod tidy (also pulls the matching kai-core forward), build/test, commit to main, then tag the next kai-cli patch. That tag drives the existing ci.yml build + publish. Pure versioned bump (no replace), so the boundary job stays green. Bot pushes the bump commit + tag directly to main. Hardening: dispatch version validated against strict semver via a quoted env var (no injection); release is atomic + retry-safe (commit + tag via one `git push --atomic`, idempotency keyed on the tag so an untagged bump resumes instead of being dropped), patch math is base-10 (no octal trap), the commit stages only go.mod/go.sum, and tag collisions are skipped.
fatihacet
force-pushed
the
automation/release-please
branch
from
fed1486 to
67c9d73
Compare
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.
What
Make kai-cli auto-adopt and auto-release on every kai-engine release — no release-please.
.github/workflows/adopt-engine.yml: onengine-released, rungo get kai-engine@<version>+go mod tidy(also advances the transitive kai-core), build/test, commit the bump to main, then tag the next kai-cli patch. That tag triggers the existingci.yml, which builds the binaries and publishes to GCS + GitHub Releases.Cascade
Also runnable manually:
gh workflow run adopt-engine.yml -R kaicontext/kai-cli -f version=vX.Y.Z.Notes
replaceis added, soci.yml'sboundaryjob stays green.v*tag;concurrencyguards against overlapping releases.Requires (GitHub settings — not in this PR)
KAI_CORE_APP_*secrets on this repo (already present).Part of the auto-release set across kai-core / kai-engine / kai-cli / kai-tui / kai-server.