Skip to content

chore: merge release/2.43.0 into develop for tag ancestry#22138

Open
HashWrangler wants to merge 3 commits intodevelopfrom
jd/chore-merge-release-2.43.0-develop-tag-ancestry
Open

chore: merge release/2.43.0 into develop for tag ancestry#22138
HashWrangler wants to merge 3 commits intodevelopfrom
jd/chore-merge-release-2.43.0-develop-tag-ancestry

Conversation

@HashWrangler
Copy link
Copy Markdown
Collaborator

Summary

Merges the primary minor line branch release/2.43.0 into develop so 2.43.0 semver tags (GA and pre) are reachable in develop ancestry for Go module pseudo-version selection.

Scope

  • In: primary minor release branch release/2.X.0 — here release/2.43.0 only.
  • Out of scope for this PR: 2.44.0 (handled elsewhere), patch/hotfix lines such as release/2.43.1 / release/2.43.2 (not in this change).

Why

Without this merge, v2.43.0, v2.43.0-rc.0, and v2.43.0-beta.0 are not ancestors of develop even when trunk has moved forward. Go pseudo-version bases are derived from reachable semver tags in commit history, not from file-level parity or closed merge-back PRs.

What changed in the tree

  • Merge origin/release/2.43.0 into develop (ancestry-preserving).
  • Conflicts resolved in favor of current develop trunk for package.json / CHANGELOG (trunk version remains 2.44.0; no downgrade).
  • The release/2.43.0 line (including the tagged bump commit) is now in the merge history so the 2.43.0 tags are ancestors of the result.

Verification (local)

git merge-base --is-ancestor v2.43.0 HEAD   # true after this merge
git merge-base --is-ancestor v2.43.0-rc.0 HEAD
git merge-base --is-ancestor v2.43.0-beta.0 HEAD

Refs

  • AGENTS/release-marshal/outputs/pseudo-version-develop-ancestry-2026-04-22.md (control-plane; ancestry analysis).

github-actions Bot and others added 2 commits April 14, 2026 18:28
Merges primary minor line release/2.43.0 so v2.43.0 semver tags are
ancestors of develop for Go pseudo-version selection. Conflicts resolved
in favor of current develop trunk (package.json/CHANGELOG).

Co-authored-by: release-marshal <ops-control-plane>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 22, 2026

✅ No conflicts with other open PRs targeting develop

@HashWrangler HashWrangler force-pushed the jd/chore-merge-release-2.43.0-develop-tag-ancestry branch from 353661b to 9a6512d Compare April 22, 2026 20:28
@HashWrangler HashWrangler marked this pull request as ready for review April 22, 2026 20:30
Copilot AI review requested due to automatic review settings April 22, 2026 20:30
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

@HashWrangler HashWrangler requested review from bolekk and jmank88 April 22, 2026 20:31
@HashWrangler HashWrangler enabled auto-merge April 22, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants