chore(deps): bump bigbluebutton-html-plugin-sdk to 1.0.0-beta.2 (BigBlueButton 4.0) - #144
Open
imdt-claudiop wants to merge 1 commit into
Open
imdt-claudiop wants to merge 1 commit into
imdt-claudiop wants to merge 1 commit into
Conversation
…lueButton 4.0) The plugin SDK moves to its first 1.x pre-release, published on npm as 1.0.0-beta.2 and shipped by BigBlueButton 4.0. Two version fields change here, and they mean different things: - package.json pins the SDK that builds the bundle. The semver operator already used by this repository is preserved, so a pinned dependency stays pinned and a caret range stays a caret range. - manifest.json requiredSdkVersion declares the range of server SDK versions this plugin supports. When a meeting starts, BigBlueButton checks its own html5PluginSdkVersion against that range and records a plugin load failure when it does not match. It becomes ^1.0.0-beta.2, following the caret convention already used on the 0.1.x line, which keeps expressing compatibility as the SDK reaches 1.x. The lock file is regenerated so the resolved SDK matches the new declaration. Co-Authored-By: Guilherme Pereira Leme <69865537+GuiLeme@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Bumps
bigbluebutton-html-plugin-sdkon the v0.1.x branch to 1.0.0-beta.2, fromthe SDK's 1.x pre-release line published on npm (dist-tag
beta).Two version fields change, and they mean different things:
package.jsonselects the SDK the bundle is built against. The semver operatoralready used by this repository is preserved: a pinned version stays pinned, a
caret range stays a caret range.
requiredSdkVersioninmanifest.jsondeclares the range of server SDKversions this plugin supports. It becomes
^1.0.0-beta.2, keeping the caretconvention this line already uses; that is the semantically correct range for
the 1.x SDK line.
package-lock.jsonis regenerated so the resolved SDK matches the new declaration.The README compatibility table's SDK column for the v0.1.x row moves to
v1.0.0-beta.x. The lock regeneration also drops npm-generated
libcmetadataarrays from some optional platform-specific packages; this is metadata churn from
the npm version used, with no dependency change.
Motivation
This branch targets BigBlueButton 4.0, which adopts the 1.x SDK with the
core-side bump (bigbluebutton/bigbluebutton#25803). Building and declaring
compatibility against the same SDK keeps the plugin in step with that change.
More
Known limitation, declared on purpose: BigBlueButton servers cannot evaluate this
manifest range yet. The server-side version check (bbb-apps-akka) uses a semver
library whose range parser rejects prerelease identifiers, so any range containing
a prerelease tag fails with "Unexpected error while parsing SDK versions: Illegal
character near 'beta.2'" and the plugin is not loaded. The range stays
^1.0.0-beta.2because it is the correct declaration for the 1.x line; the pluginwill load once the core-side parser fix lands.
Validation: npm ci, TypeScript check, bundle build and lint are green against the
new SDK on the Node version this repository's CI uses. On a BigBlueButton 4.0 test
server already running SDK 1.0.0-beta.2, the parser failure above was reproduced,
and a probe that temporarily widened the served manifest range confirmed a bundle
built against SDK 1.0.0-beta.2 loads cleanly, so the range parser is the only
blocker.