Skip to content

chore(legacy)!: remove legacy API support and WebRTC - #1589

Merged
barhanc merged 5 commits into
mainfrom
chore/remove-legacy-and-webrtc
Oct 30, 2026
Merged

barhanc merged 5 commits into
mainfrom
chore/remove-legacy-and-webrtc

Conversation

@barhanc

@barhanc barhanc commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Description

Removes the legacy API, example apps, resource fetcher packages, WebRTC package, and legacy documentation. Cleans up native bindings, build configuration, publishing workflows, dependencies, and tests.

Introduces a breaking change?

  • Yes
  • No

Type of change

  • Bug fix (change which fixes an issue)
  • New feature (change which adds functionality)
  • Documentation update (improves or adds clarity to existing documentation)
  • Other (chores, tests, code style improvements etc.)

Tested on

  • iOS
  • Android

Testing instructions

  • Clean-build the computer vision, NLP, and speech example apps on Android and iOS.
  • Launch each app and confirm native initialization succeeds.
  • Confirm archived versioned documentation is correct.

Screenshots

Related issues

Closes #1421

Checklist

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly
  • My changes generate no new warnings

Additional notes

@barhanc barhanc self-assigned this Oct 29, 2026
@barhanc barhanc added the chore PRs that are chores label Oct 29, 2026
@barhanc
barhanc requested a review from msluszniak October 29, 2026 16:23
@barhanc
barhanc marked this pull request as ready for review October 29, 2026 16:30
@msluszniak

Copy link
Copy Markdown
Member

@barhanc Do we want to merge this one pretty much immediately or right before the v1.0.0 release? If we want to do it now, then potential patches for v0.11.x will be stripped from the legacy part, while v0.11.0 will have it.

@barhanc

barhanc commented Oct 29, 2026

Copy link
Copy Markdown
Member Author

We don't have to cherry-pick the commit with this change when releasing the patch versions so they keep the legacy path. I would merge this as early as possible, so that we work on the lib structure that is the target one.

@msluszniak

msluszniak commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

We don't have to cherry-pick the commit with this change when releasing the patch versions so they keep the legacy path. I would merge this as early as possible, so that we work on the lib structure that is the target one.

Fair enough. I'm checking this rn. You can handle the conflict in the meantime ;)

@msluszniak

Copy link
Copy Markdown
Member

Ok, I've completed full passes over all demo apps on android and iOS (both real devices and simulators) and everything seemed to worked correctly. Now the docs pass and we are good to go.

@msluszniak msluszniak left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🚀

@barhanc
barhanc merged commit 9f3bbd8 into main Oct 30, 2026
7 checks passed
@barhanc
barhanc deleted the chore/remove-legacy-and-webrtc branch October 30, 2026 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore PRs that are chores

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tracking: remove the legacy API layer in future release

2 participants