// Bump YugabyteDB latest_stable in yb-versions.json, coordinate Jenkins migtest cluster upgrades, fix version-gated issue/integration tests, and open a PR only after all GitHub Actions pass. Use when updating latest stable YB version, yb-versions.json, Jenkins YB cluster, or Voyager supported YB versions.
Generate yb-voyager release notes from a commit range, formatted like the YugabyteDB Voyager release-notes docs page. Use when the user asks to draft release notes, summarize a release, or write what's-new entries for a voyager version.
Review all code changes on the current branch compared to main, applying hierarchical BUGBOT.md and .cursor/BUGBOT.md guidelines from each changed file's directory up to the repo root. Use when the user asks to review a branch, review changes, compare against main, do a code review, or check branch diff.
Interactive git rebase workflow with conflict-by-conflict review. Use when the user asks to rebase a branch, rebase onto main, resolve rebase conflicts, or update a branch with upstream changes.
Post a single non-blocking GitHub PR review with inline line-anchored comments generated by the agent. Every comment is prefixed with `[cursor]` so reviewers can tell they are AI-generated. Only Critical and Warning findings are posted; Suggestions / Nice-to-haves / Good-to-haves are never sent. Use when the user asks to "post the review on GitHub", "post these comments on the PR", "post the findings as PR comments", or otherwise wants an in-chat code review persisted on a GitHub pull request. Typically runs as a follow-up to the `branch-review` skill but does not require it.
Create and update GitHub pull request descriptions using the project PR template. Use when the user asks to create a PR, write a PR description, update a PR description, or manage pull requests.
| name | update-yb-latest-stable |
| description | Bump YugabyteDB latest_stable in yb-versions.json, coordinate Jenkins migtest cluster upgrades, fix version-gated issue/integration tests, and open a PR only after all GitHub Actions pass. Use when updating latest stable YB version, yb-versions.json, Jenkins YB cluster, or Voyager supported YB versions. |
Single source of truth: yb-voyager/versions/yb-versions.json. GitHub Actions read it via .github/workflows/prepare-versions.yml. Jenkins migtests use a separate long-lived YB cluster (env vars), not this file directly.
2025.2.4.0-b150).yugabytedb/yugabyte:<tag>.update-yb-latest-stable-<version> (e.g. update-yb-latest-stable-2025.2.4.0).yb-versions.jsonEdit yb-voyager/versions/yb-versions.json. How you change version[] depends on the bump type.
Always set latest_stable to the new full tag (e.g. 2025.2.4.0-b150).
2025.2.3 → 2025.2.4)Replace the existing entry for that series in place; do not prepend a second 2025.2.* line.
// Before
"version": ["2025.2.3.0-b149", "2025.1.3.2-b1", ...],
"latest_stable": "2025.2.3.0-b149"
// After
"version": ["2025.2.4.0-b150", "2025.1.3.2-b1", ...],
"latest_stable": "2025.2.4.0-b150"
2025.2 becomes latest stable)Prepend the new series tag to version[]. Keep older series (e.g. 2025.1.*) in the list for CI matrix coverage unless maintainers retire them.
// Before
"version": ["2025.1.3.2-b1", "2024.2.8.0-b85", ...],
"latest_stable": "2025.1.3.2-b1"
// After — prepend 2025.2.*, keep 2025.1.*
"version": ["2025.2.3.0-b149", "2025.1.3.2-b1", "2024.2.8.0-b85", ...],
"latest_stable": "2025.2.3.0-b149"
Only remove an older series entry when the team explicitly drops Voyager support for that release line.
Rare — only when bumping version[] for matrix coverage while latest_stable stays on another tag. Coordinate with maintainers.
latest_stable must exactly match one entry in version (enforced in prepare-versions.yml).version[] (e.g. one 2025.2.*, not both 2025.2.3 and 2025.2.4 — use in-place replace for that case).A.B.C.D-b<N> (four numeric segments + build).latest_stable (usually no edit)These read yb-versions.json at build/runtime — no change for a typical bump:
yb-voyager/versions/versions.go (GetLatestStableYBVersion, embedded JSON)yb-voyager/src/ybversion/constants.go — LatestStable is set from versions.GetLatestStableYBVersionWithoutBuildNumber() in init()prepare-versions outputs (yb_latest_stable, yb_versions matrix)YB version bumps often change error messages or fix issues. Always run and fix the issue integration tests before opening the PR.
From yb-voyager/:
export YB_VERSION=$(jq -r '.latest_stable' versions/yb-versions.json)
# All supported versions (matches CI issue-tests matrix)
for v in $(jq -r '.version[]' versions/yb-versions.json); do
echo "=== DDL issues @ $v ==="
YB_VERSION="$v" go test -tags issues_integration -run '^TestDDLIssuesInYBVersion$' -count=1 -timeout=30m ./src/query/queryissue/
echo "=== DML issues @ $v ==="
YB_VERSION="$v" go test -tags issues_integration -run '^TestDMLIssuesInYBVersion$' -count=1 -timeout=30m ./src/query/queryissue/
done
# Latest-stable-only tag (CI also runs this)
go test -tags 'issues_integration,yb_version_latest_stable' -count=1 -timeout=30m ./src/query/queryissue/...
Files to inspect when tests fail:
yb-voyager/src/query/queryissue/issues_ddl_test.go — TestDDLIssuesInYBVersionyb-voyager/src/query/queryissue/issues_dml_test.go — TestDMLIssuesInYBVersionyb-voyager/src/query/queryissue/issues_ddl.go / issues_dml.go — MinimumVersionsFixedIn, issue definitionsyb-voyager/src/query/queryissue/issues_ddl_test.go — assertErrorCorrectlyThrownForIssueForYBVersionFor each failure:
-run 'TestDMLIssuesInYBVersion/copy_from_where' (or the failing t.Run name).err from conn.Exec; YB may return a different message or no error on newer builds.issue.IsFixedIn(testYbVersion) — if the issue is marked fixed for this series, tests expect success (assert.NoError), not the old error string.ybversion.V2025_2_3_0, packaging.version.Version in migtest validate scripts).ybversion constants in src/ybversion/constants.go only when tests compare against a new V* constant.TestDDLIssuesInYBVersion / TestDMLIssuesInYBVersion for that YB_VERSION.External YB (matches local psql instead of testcontainers):
export YB_CONN_STR="postgresql://yugabyte:yugabyte@127.0.0.1:5433/yugabyte?sslmode=disable"
YB_VERSION=$(jq -r '.latest_stable' versions/yb-versions.json)
go test -tags issues_integration -run '^TestDMLIssuesInYBVersion$' -count=1 -v ./src/query/queryissue/
Run and fix as needed (do not ignore red CI):
| Test area | Command / workflow |
|---|---|
| Issue tests (all) | go test -tags issues_integration ./src/query/queryissue/... |
| Latest-stable tag | go test -tags yb_version_latest_stable ./... |
| Integration / live migration | .github/workflows/integration-tests.yml |
| Failpoints | .github/workflows/failpoint-tests.yml |
| Migtests | pg-13-migtests, pg-17-migtests, mysql-migtests, misc-migtests |
| Unit | go test -tags unit ./... |
If any test fails: reproduce locally, root-cause against the new YB behavior, fix test expectations or product code in this PR, re-run until green. Do not merge with failing or skipped issue tests.
rg "2025\.2\.3|V2025_2_3|latest_stable" yb-voyager migtests
| Area | When to touch |
|---|---|
yb-voyager/src/ybversion/constants.go | New 3-dot gate needed |
migtests/tests/**/validate | Version-specific extension or behavior checks |
yb-voyager/config-templates/*.yaml | Docs mention minimum YB version |
yb-voyager/cmd/*.go help text | User-facing minimum version strings |
Jenkins config is not in this repo. Migtests run via migtests/scripts/jenkins-wrapper against a cluster set by Jenkins job env vars (TARGET_DB_HOST, TARGET_DB_PORT, etc. — see migtests/scripts/yugabytedb/env.sh defaults).
Required (human / infra):
<NEW_VERSION> (same build as latest_stable).psql "postgresql://yugabyte:<password>@<TARGET_DB_HOST>:<TARGET_DB_PORT>/yugabyte" \
-c "SELECT version();"
PR description must note: Jenkins cluster upgraded (or infra ticket) and Jenkins job name + result.
Do not change migtests/scripts/yugabytedb/env.sh default host unless intentionally moving the shared dev cluster for everyone.
Push branch and create PR to main. Use the pr-description skill.
git push -u origin HEAD
gh pr checks --watch
gh pr checks --json name,state,link --jq '.[] | select(.state != "SUCCESS")'
Use the babysit skill to fix CI failures in a loop (do not weaken workflows to force green).
TestDDLIssuesInYBVersion passes for every entry in yb-versions.json version[] (run locally before push; confirmed green in Issue Tests workflow)TestDMLIssuesInYBVersion passes for every entry in version[] (same)yb_version_latest_stable issue tests pass (go test -tags yb_version_latest_stable ./src/query/queryissue/...)| Workflow | What it exercises |
|---|---|
Go | Unit tests, staticcheck |
Build Voyager | Installer / build |
Integration Tests | Live migration @ yb_latest_stable |
Failpoint Tests | Failpoint flows @ yb_latest_stable |
Issue Tests | DDL/DML issue tests matrix over all version[] + yb_version_latest_stable |
PG 13: Migration Tests | Migtests matrix per yb_versions |
PG 17: Migration Tests | Migtests matrix per yb_versions |
MySQL: Migration Tests | Migtests matrix per yb_versions |
Misc Migration Tests | Import-file tests per yb_versions |
| Failure | Likely fix |
|---|---|
prepare-versions — latest_stable not in version | Fix JSON alignment |
TestDDLIssuesInYBVersion / TestDMLIssuesInYBVersion | Update assertErrorCorrectlyThrownForIssueForYBVersion expected strings, MinimumVersionsFixedIn, or version branches |
| Issue tests — testcontainers vs local YB differ | Use YB_CONN_STR for local cluster; document docker image gap |
Migtests — extension list in validate | Version-gate expectedExtensions (e.g. pg_parquet only before 2025.2.3) |
| Integration tests — image pull | Ensure yugabytedb/yugabyte:<tag> exists |
chore: bump latest stable YugabyteDB to <NEW_VERSION>