Skip to content

Carry the legacy Google route deprecation into redesign main (#746) - #769

Merged
thomasluizon merged 1 commit into
redesign/mainfrom
thomasluizon/ticket-746-carry-deprecation
Oct 19, 2026
Merged

thomasluizon merged 1 commit into
redesign/mainfrom
thomasluizon/ticket-746-carry-deprecation

Conversation

@thomasluizon

Copy link
Copy Markdown
Owner

Carries one main commit into redesign/main ahead of the rest of the #746 carry (orbit-api#768), so the legacy Google auth routes are deprecated on redesign/main before the carry removes them.

Part of thomasluizon/orbit-tickets#746 (the orbit-api main to redesign/main sync).

Why a separate pull request

orbit-api#768 carries both 21f810ff (#753, deprecate POST /api/Auth/google and POST /api/Auth/operations/google) and #752 (remove them) in one squash. Its OpenAPI Breaking-Change Gate compares against redesign/main, where the routes are not deprecated yet, and fails with api path removed without deprecation for both routes. main passed the same gate because #753 merged before #752. This pull request repeats that order on redesign/main; orbit-api#768 then takes one base merge.

Carried

  • 21f810ff Deprecate legacy Google auth routes (thomasluizon/orbit-tickets#1528, part 1) (#753), cherry-picked with -x, applied cleanly. No other change.

Test evidence

  • dotnet build Orbit.slnx: exit 0.
  • dotnet test tests/Orbit.Domain.Tests: 744 passed, exit 0.
  • dotnet test tests/Orbit.Application.Tests: 5,705 passed, exit 0.
  • dotnet test tests/Orbit.Infrastructure.Tests: 3,678 passed, exit 0.

Assumptions

  • None.

Manual steps

  • None. The routes stay served; only their OpenAPI deprecated flag and the controller attribute change.

🤖 Generated with Claude Code

* Deprecate legacy Google auth routes for #1528

* Explain deprecated Google auth routes and annotate legacy tests

(cherry picked from commit 21f810f)

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ No new issues found.

Reviewed changes: Reviewed the complete deprecation carry into redesign/main, including the existing OpenAPI transformer and affected consumer references.

  • Legacy routes preserved: Both Google token-based actions gain [Obsolete] messages pointing to the existing authorization-code routes, without changing routing, protection, request contracts or responses.
  • Versioned documentation: Both OpenAPI documents mark the two legacy POST operations as deprecated and remain unchanged after regeneration.
  • Regression coverage: Added route/deprecation assertions and retained legacy success/failure coverage; the focused AuthControllerTests and ApiVersioningTests run passed all 136 tests. The full solution suite was not rerun.

Pullfrog  | View workflow run | Using gpt-6.1-sol | 𝕏

@sonarqubecloud

Copy link
Copy Markdown

@thomasluizon
thomasluizon merged commit 501c8ee into redesign/main Oct 19, 2026
21 checks passed
@thomasluizon
thomasluizon deleted the thomasluizon/ticket-746-carry-deprecation branch October 19, 2026 06:41
thomasluizon added a commit that referenced this pull request Oct 19, 2026
… supersedes

The base merge brought #769's assertions that POST /api/Auth/google and
POST /api/Auth/operations/google stay available and deprecated. This carry
removes both routes (main's #1528 part 2), so those assertions no longer
have a subject.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
thomasluizon added a commit that referenced this pull request Oct 19, 2026
…, slip contract and the Supabase sign-in removal (#768)

* Stop Stripe and Play renewals when account deletion is confirmed (#746)

* fix: stop subscription renewal when account deletion is confirmed

* fix: restrict renewal restoration to an unexpired paid period

* fix: keep free account deletion independent of billing services

* fix: bound billing cancellation delays during account erasure

* fix: preserve renewal intent during deletion reconciliation

(cherry picked from commit 85d8824)

* docs: name Render web services in version floor preconditions (#755)

(cherry picked from commit 21615aa)

* fix(infra): use Render for production database connections (#754)

(cherry picked from commit e2909b6)

* test(habits): cover end date reactivation allowance through handler (#759)

(cherry picked from commit 16203d9)

* test(mcp): verify Pro access for OAuth and API keys (#760)

(cherry picked from commit 0a90f67)

* Cover calendar auto-sync scheduling and import reconciliation (ORB-199) (#761)

* test(calendar): cover auto-sync scheduler eligibility and batching

* test(calendar): cover import suggestion reconciliation filters

* test(calendar): isolate free plan eligibility from expiry

(cherry picked from commit 664c756)

* Clarify controller action cross-references in the agent catalog (#762)

(cherry picked from commit d9cda52)

* refactor(calendar): share legacy match key for sync and suggestions (#763)

(cherry picked from commit 8e754c4)

* Contract habit log slip classification schema (#718) (#764)

(cherry picked from commit b0d3ff4)

* fix(calendar): gate recurring event reconciliation (#765)

(cherry picked from commit c900dba)

* Gate rolling schema contractions behind deployment barriers (#766)

* feat: require deployment barriers for rolling schema contractions

* fix: keep quoted SQL comment markers from hiding contractions

* test: record the deployed habit log contract barrier

* ci: run the rolling contract gate only when its inputs change

The gate builds the infrastructure test project, which costs minutes on every
pull request. It now runs only when a migration, the barrier file or the gate
itself changes; the step before it already reads the same diff.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: require barriers for unclassified ALTER TABLE actions

* test: isolate barrier unit coverage from checkout history

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 626c525)

* fix: require a session claim on access tokens (#767)

(cherry picked from commit 517ed1b)

* Deprecate legacy Google auth routes (#1528, part 1) (#753)

* Deprecate legacy Google auth routes for #1528

* Explain deprecated Google auth routes and annotate legacy tests

(cherry picked from commit 21f810f)

* Remove deleted Supabase sign-in path (#1528) (#752)

* Remove deleted Supabase sign-in path (#1528)

* Remove unused access-token validation catalog entries (#1528)

(cherry picked from commit 141a4a2)

* fix: bind carried schema barrier to the deployed redesign

Record the observed staging deployment and its drained predecessors without changing the migration gate. Regenerate the tracked gating matrix for the combined source. Refs thomasluizon/orbit-tickets#746.

* fix: retain deletion cancellation ownership across provider retries (#770)

* fix: persist deletion cancellation ownership before provider updates

* test: cover deletion intent commit and account changes

* fix: identify deletion-owned Stripe cancellations

Reconcile provider metadata before restoring renewal or retaining ownership, reject open cancellation transactions, and log skipped erasure rechecks.

Refs thomasluizon/orbit-tickets#1547

(cherry picked from commit a7d1cf2)

* test: drop the deprecation assertions the legacy Google route removal supersedes

The base merge brought #769's assertions that POST /api/Auth/google and
POST /api/Auth/operations/google stay available and deprecated. This carry
removes both routes (main's #1528 part 2), so those assertions no longer
have a subject.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant