Skip to content

feat(specs): remove migratedAbTestID from abtesting-v3 - #6883

Open
cdhawke wants to merge 2 commits into
mainfrom
chore/deprecate-migrated-abtest-id
Open

feat(specs): remove migratedAbTestID from abtesting-v3#6883
cdhawke wants to merge 2 commits into
mainfrom
chore/deprecate-migrated-abtest-id

Conversation

@cdhawke

@cdhawke cdhawke commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

🧭 What and Why

🎟 JIRA Ticket: OPTIM-2329

algolia/go#26972 is merged and deployed

Breaking: removes migratedAbTestID from the abtesting-v3 ABTest schema, so it disappears from all eight generated clients.

The field exists only for the one-off US→EU A/B test region migration, which finished in 2024. Measured on abtests-prod-europe-west3:

Measure Value
Rows carrying a value 1,408 across 226 apps
Newest created_at 2024-03-05
Still active 0
Same on abtests-prod-us-east1 0

Nothing has been written for 2.4 years, and nothing reads it: the dashboard's last reference went in AlgoliaWeb#29783, and the API stops emitting it in algolia/go#26972.

Changes included:

  • Removes the migratedAbTestID property from ABTest and the MigratedABTestId schema it referenced.

Deliberately a removal rather than a deprecation. A deprecation marker promises removal, and there is no migration path to signal — the field has no successor and no remaining consumer, so the notice would only add noise to eight clients' typedefs.

🧪 Test

Green CI. Spec-only, so no generated code is included, per the CI note that generated code is pushed at the end of the run.

Locally verified with yaml.safe_load: the MigratedABTestId schema and the migratedAbTestID property are both gone, no dangling $ref remains, ABTest.required is unchanged, and the property count drops from 10 to 9.

Needs a release note calling out the removal.

@algolia-api-clients-automation-bot

algolia-api-clients-automation-bot Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

💥 Breaking changes detected !!

Either this PR or a previous PR not released yet introduced breaking changes, be careful when merging.
You can find the details in the 'client java@21' CI job.

✔️ Code generated!

Name Link
🪓 Triggered by b105e187ba60b8709033f5dba6b13d2c5b50dd7c
🍃 Generated commit 41d586841986429c5f40151481b517aab99c44ae
🌲 Generated branch generated/chore/deprecate-migrated-abtest-id
📊 Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language Req/s
javascript 2500
php 2116
go 1795
csharp 1344
python 1248
swift 1075
java 1058
ruby 867
scala 817

@cdhawke
cdhawke force-pushed the chore/deprecate-migrated-abtest-id branch from 3777f61 to 5aa0df7 Compare August 11, 2026 21:36
@cdhawke cdhawke changed the title chore(specs): deprecate migratedAbTestID feat(specs)!: remove migratedAbTestID from abtesting-v3 Aug 11, 2026
BREAKING CHANGE: the migratedAbTestID field is removed from the ABTest
response schema, so it disappears from all generated clients.

The field exists only for the one-off US->EU A/B test region migration, which
finished in 2024. Nothing has been written for 2.4 years: the newest row
carrying a value on abtests-prod-europe-west3 was created 2024-03-05, all
1,408 of them are in a terminal state, and zero rows carry it in us-east1.

Nothing reads it either. The dashboard's last reference went in
AlgoliaWeb#29783, and the API stops emitting it in algolia/go#26972.

Order matters: ABTest is additionalProperties: false, so removing the
property while the API still sends it would make this spec declare those
responses invalid. algolia/go#26972 must be merged and deployed first.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@cdhawke
cdhawke force-pushed the chore/deprecate-migrated-abtest-id branch from 5aa0df7 to 3876d9f Compare August 12, 2026 00:15
@cdhawke cdhawke changed the title feat(specs)!: remove migratedAbTestID from abtesting-v3 feat(specs): remove migratedAbTestID from abtesting-v3 Aug 20, 2026
@cdhawke
cdhawke requested review from a team, Niamsy and stevenMevans August 20, 2026 19:31
@cdhawke
cdhawke marked this pull request as ready for review August 20, 2026 19:31
@cdhawke
cdhawke requested a review from a team as a code owner August 20, 2026 19:31
@cdhawke

cdhawke commented Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

@Fluf22 @MarioAlexandruDan could you have a look at this when you get some time? 🙏🏻

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.

2 participants