WIP: Release/sdk/11 #508
Merged
WIP: Release/sdk/11 #508
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
Forward comp/block item summary
Forward comp/chain updates
Forward comp/special events
Forward comp/events
Jira-Id: COR-1841
Jira-Id: COR-1841
* Add `CborContractAddress` type * Add unit tests for `CborContractAddress`
merge `main` into `release/sdk/11`
…-sdk-js into cis7-refactor
WIP: CIS-7 implementation
Make everything optional for token init params + module state, according to CIS-7
Co-authored-by: Doris Benda <[email protected]>
Align cis-7 decode function with changes to init params and module state
* Create app token, and use it to push docs to gh-pages * rm whitespace from comment * Fix broken links and linkcheck in docs * Update wasm pack + rust version (#519) * 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 * changing tar fs version as per dependabot suggestion * removed the entry from resolutions package.json ran yarn up @size-limit/preset-big-lib ran yarn estimo --recursive * Updated babel traverse using yarn up @babel/traverse -R * ran yarn up form-data -R changed from 3.0.1 to 3.0.4, npm audit locally not complaining anymore * updated path-to-regexp version this one needed to be done via resolutions in package.json could not update via yarn commands * upgraded body-parser version to 1.20.3 had to use resolutions to upgrade. yarn upd body-parser and the parents did not update body parser stayed at 1.20.2 * removed path-to-regexp and body-parser from resolutions ran yarn upd -R express. express is updated and the two children got updated * ran yarn upd ws -R to make sure no version of ws between 8 and 8.17.1 confirmed the versions used via yarn why * ran yarn upd -R rollup checked that the rollup version is 2.79.2 and nothing lower No vulnerability alert highlighted when npm audit is run * updated http-proxy-middleware to 2.0.9 after running yarn upd http-proxy-middleware -R it was 2.0.6 beforehand which is marked as vulnerable --------- Co-authored-by: Stefan Madsen <[email protected]> Co-authored-by: Stefan Madsen <[email protected]> Co-authored-by: Richard B <[email protected]> Co-authored-by: rbaconcordium <[email protected]>
Sdk 11 merge `main`
limemloh
approved these changes
Oct 13, 2025
sdk version bump to 11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Next major release of
@concordium/web-sdkChanges
Checklist
hard-to-understand areas.