Skip to content

feat(loader): Make JavaScript v11 available in the backend - #123893

Draft
msonnb wants to merge 1 commit into
masterfrom
ms/v11-loader-backend
Draft

feat(loader): Make JavaScript v11 available in the backend#123893
msonnb wants to merge 1 commit into
masterfrom
ms/v11-loader-backend

Conversation

@msonnb

@msonnb msonnb commented Sep 9, 2026

Copy link
Copy Markdown
Member

Make JavaScript SDK 11.x available in the loader version choices while keeping the default loader version at 10.x. Match the complete major version when resolving SDK releases so 10.x and 11.x each resolve to their own latest stable release.

Deployment order: merge this backend PR only after the companion frontend PR has been merged and deployed to production. Merging the frontend alone is not sufficient; its v11 loader controls must be deployed before this backend exposes 11.x as a selectable version.

Regression coverage checks v11 availability, stable release selection, and the unchanged default loader version.

Frontend prerequisite: #123892.

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Sep 9, 2026
@msonnb msonnb added the Do Not Merge Don't merge label Sep 9, 2026
@msonnb
msonnb requested a review from andreiborza September 9, 2026 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Merge Don't merge Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants