Forward comp/migration guide #537
Merged
Conversation
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
Create app token, and use it to push docs to gh-pages
Fix broken links and linkcheck in docs
* move wasm-pack out of local deps * update wasm-bindgen * use rust version 1.85 * declare wasm-pack as a dependency in readme section * install wasm-pack in workflows * Fix module resolution due to rust-bindings package cjs->esm * Fix CRA example app warnings * Update sdk changelog
ran yarn up @size-limit/preset-big-lib ran yarn estimo --recursive
changing tar fs version as per dependabot suggestion
changed from 3.0.1 to 3.0.4, npm audit locally not complaining anymore
this one needed to be done via resolutions in package.json could not update via yarn commands
had to use resolutions to upgrade. yarn upd body-parser and the parents did not update body parser stayed at 1.20.2
Updated babel traverse using yarn up @babel/traverse -R
Changing form data to version 3.0.4 from 3.0.1, npm audit no longer complaining
Upgraded the path-to-regexp version to deal with the critical vulnerability alert
ran yarn upd -R express. express is updated and the two children got updated
Upgraded body parser version to 1.20.3 due to vulnerability alert
confirmed the versions used via yarn why
Ensuring no WS version between 8 and 8.17.1 used due to vulnerability alert
checked that the rollup version is 2.79.2 and nothing lower No vulnerability alert highlighted when npm audit is run
Ensuring rollup version is 2.79.2 and nothing lower
after running yarn upd http-proxy-middleware -R it was 2.0.6 beforehand which is marked as vulnerable
updated http-proxy-middleware to 2.0.9
td202
approved these changes
Oct 9, 2025
Co-authored-by: Thomas Dinsdale-Young <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Purpose
Adds a migration guide to version 11 of the SDK, mostly explaining how to handle
Upward