Bump version to 0.30.0-rc.0

[Magmusacy]

Bumps the package version to 0.30.0-rc.0 ahead of a prerelease.

Why

The v0.29.0-rc.1 release failed to publish: package.json was still at 0.29.0, which is already on npm, so npm publish exited with E403 You cannot publish over the previously published versions: 0.29.0. The published version comes from package.json, not from the tag name — so the version has to be bumped in the repo first.

0.30.0-rc.0 (minor, prerelease) covers the VoIP work merged in #78 and sorts above 0.29.0 in semver, unlike 0.29.0-rc.1.

Changes

• package.json / package-lock.json: 0.29.0 -> 0.30.0-rc.0

After merge

1. Delete the stale release/tag: gh release delete v0.29.0-rc.1 --cleanup-tag
2. Cut the prerelease against this commit: gh release create v0.30.0-rc.0 --target master --generate-notes --prerelease — the publish workflow adds --tag rc, so npm latest stays at 0.29.0.
3. In web-client-sdk, pin the submodule to v0.30.0-rc.0 (its check:webrtc-published requires the submodule tag to match this version and be on npm).

[Copilot]

Pull request overview

This PR bumps the npm package version to 0.30.0-rc.0 to ensure the prerelease can be published successfully (npm publish uses package.json’s version, not the git tag).

Changes:

• Update package.json version from 0.29.0 to 0.30.0-rc.0.
• Update package-lock.json version entries to match 0.30.0-rc.0.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Bumps the published package version to 0.30.0-rc.0.
package-lock.json	Keeps lockfile version fields in sync with the new package version.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MiloszFilimowski]

Please release from a dedicated branch. not master