chore(release-3.7): upgrade go-web to 0.2.1 and web-core to 0.20.1#929
Merged
Conversation
Change-Id: Icb05ba1df03c7dc3bfb8ffc1ff381d2eeb13dcfb
Dugyu
requested review from
Huxpro,
MoonfaceX,
SoonIter,
colinaaa and
toretto-wt
as code owners
✅ Deploy Preview for lynx-doc ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Lynx Compat Data StatsLynx Platform API: 953 Platform Coverage
Lynx Platform API
Other
Generated at 2026-04-17T09:17:53.966Z |
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.
Backport dependency upgrades to align with the web-core 0.20 WASM architecture, reducing memory usage by ~40%.
Changes
@lynx-js/go-web(github:lynx-community/go-web(0.1.0)→ 0.2.1@lynx-js/web-core→ 0.20.1Why pin to npm release
Previously
@lynx-js/go-webwas referenced asgithub:lynx-community/go-webwith no commit or tag pin. Deleting the lock file would silently pull HEAD, potentially breaking theweb-core >= 0.20.0compatibility requirement. Switching to the npm-published version makes the constraint explicit and lock-file-independent.Migration notes
@lynx-js/go-web0.2.0 drops the@lynx-js/web-elementspeer dependency and requiresweb-core >= 0.20.0.Related
Change-Id: Icb05ba1df03c7dc3bfb8ffc1ff381d2eeb13dcfb