Skip to content

release: Java SDK v6.0.0#140

Merged
saurabhjain1592 merged 2 commits into
mainfrom
release/v6.0.0
Apr 25, 2026
Merged

release: Java SDK v6.0.0#140
saurabhjain1592 merged 2 commits into
mainfrom
release/v6.0.0

Conversation

@saurabhjain1592

Copy link
Copy Markdown
Member

Summary

Major release — driven by a single observable-contract change.

`WebhookSubscription.equals()` and `.hashCode()` are now identity-based on `id`, not value-based on every field. The prior value-based equality was a bug — `WebhookSubscription` is an entity, not a value object — but `equals` / `hashCode` are part of the public Java contract that callers depend on for set deduplication, map lookup, and identity caches, so the fix is breaking per strict semver. See CHANGELOG `[6.0.0]` for the rationale.

The 6-arg constructor is preserved as a source-compat overload for callers building local instances; only `equals` / `hashCode` semantics changed.

Bumps

  • `pom.xml`: 5.7.0 → 6.0.0
  • CHANGELOG promoted to `[6.0.0] - 2026-04-25 — Major: WebhookSubscription identity-based equality` (BREAKING entry leads, additive entries follow)

Wire-shape baseline regen

Pin SHA bumped `bf1ca22a` → `10d44eb4`. `DynamicPolicyInfo` auto-resolves. Net 39 → 38.

Coordinated release

Ships same day as TS v6.0.0 (PolicyInfo rename — the other BREAKING SDK), Python v6.7.0 (additive — minor), Go v5.7.0 (additive — minor). The semver asymmetry is principled.

Test plan

  • CI: `./mvnw verify` passes (Java 11 / 17 / 21)
  • Wire-shape gate green with regenerated baseline
  • `validate-version-alignment.yml` reports 6.0.0 alignment
  • After merge: tag `v6.0.0`, Maven Central publish via release workflow

Major release. Driven by a single observable-contract change:
WebhookSubscription.equals() and .hashCode() are now identity-based
on id, not value-based on every field. The prior value-based equality
was a bug — WebhookSubscription is an entity, not a value object —
but equals/hashCode are part of the public Java contract that callers
depend on for set deduplication, map lookup, and identity caches, so
the fix is breaking per strict semver.

Bumps:
- pom.xml: 5.7.0 -> 6.0.0
- CHANGELOG [Unreleased] -> [6.0.0] - 2026-04-25

Wire-shape baseline regenerated against community SHA 10d44eb4 (post
platform v7.4.2 spec corrections). DynamicPolicyInfo entry auto-resolves.
Net 39 -> 38.

Coordinated v6 alignment release: ships same day as TypeScript v6.0.0,
Python v6.7.0, Go v5.7.0. The TS and Java repos needed major bumps;
Python and Go ship as minor because their changes are purely additive.
@saurabhjain1592 saurabhjain1592 added the spec-pin-bump Authorizes a wire-shape baseline openapi_specs_sha bump (otherwise CI blocks SHA changes) label Apr 25, 2026
@saurabhjain1592 saurabhjain1592 merged commit 7314dea into main Apr 25, 2026
12 checks passed
@saurabhjain1592 saurabhjain1592 deleted the release/v6.0.0 branch April 25, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spec-pin-bump Authorizes a wire-shape baseline openapi_specs_sha bump (otherwise CI blocks SHA changes)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant