Release 2.26.0 (develop) #2213
Merged
Release 2.26.0 (develop) #2213
Conversation
This file contains 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
Release 2.25.7
Release 2.25.7 (docs)
lnbc1QWFyb24
approved these changes
May 31, 2024
* Update WC versions * Feature - Replace internal Ethers functionality with Viem - Add WAGMI support module (#2203) * Replaced isAddress check from ethers * Replace Ethers BigNumber usage with browser native BigInt * Remove ethers from common * Testing package size * Working as expected! * Disable ums * Cleanup chain usage * More cleanup * Ens avatar testing * Some ethers swapped out for viem in Trezor and import map expanded * Alittle cleanup in Trezor * revert Trezor changes * All is working from old commit * Fix conflict * Remove logs * Return Address type to official check * Update versions and handle type issues * Bump Viem to latest * Add node version check and min set to 16.15.1 * Add npmrc files with engine-strict set to true to core, react and vue to ensure the node engine check is enforced * Added function for converting wei in both hex and string to eth, updated chain usage for ens and l2s, added function for handling decimel resolution with bigints * Return bignumber to core for now * cleanup and testing, removing unused code, refactor and rename to properly reflect functionality * Remove bignumber from core again * Fix merge issue with unstoppable resolution * Return getText function for ens and update to viem * Refine ci changes scope to core and related packages * Final pass of PR for cleanup and refactor * Remove ethers from tp * Update to latest viem * Update cede and WC docs * resolve conflict * Update config to publish viem test branches * Update tsconfig and types * Update node version in core * Bump versions for release and Remove console.log * ENS working again * Progress within hw wallets * Progress on chain imports * Further refinement on viem usage of public client * refine ledger, deprecate v1 * Update TS, revert viem changes to HW-wallets * Handle ts errors * Update packages for test release * Handle all ts errors! * Cleanup * Making progress * Wagmi core * Refine imports and test a whole bunch * Fix build errors * Try later version of node in CI * Add sass types to common * Update tsconfig * Update imports from common * Refine types * Update core imports * Update svelte preprocess * Bump common version * More refinements to core * Remove log * Update tsconfig for hw-common to resolve build error * Ensure new utils file is part of commit * Remove unnecessary commonjs as the issue was fixed by viem team * Use viem utils in common * Changes to versioning and ready for testing * Bump version * Merge in changes from viem branch * More updates from viem branch * Refine package intialization and wagmi init * testing signing * Update wagmi disconnect * Update viem versions * Yarn it * Update publish workflow to publish all packages * Fix issue and redeploy * Update solid node build version * Handle build errors * Update configs for build * Update ci build config * Bump arcana node version in CI * Fix arcana * Fix venly * Update gnosis pakcage.json * Get all of the changes from viem merged and stablelized * Use toHex function, switch chain now working * Handle multiple wallets correctly * Still working thru MM sdk issues * Working through issues * Still working through MM issues * Connect working for sdks * wagmi support stabilized * Cleanup logs * More updates to wagmi on disconnect * Refine disconnect * Create and test wagmi module * Create wagmi module * Add wagmi docs * Update examples * Update disconnect to handle wagmi * Handle ts errors in wagmi package * Refine examples and more ts fixes * Handle more errors * Update tags to be named as wagmi * Update CI for deployment * Fix CI build for wagmi * Update tsconfig * Update tsconfig again * Update docs examples * Fix build error * cleanup exports and hook within react and document * Refine docs * Capsule is working! * Add note about init object to docs and readme * Export all wagmi functions from wagmi package * Update docs * Fix examples * Bump to latest versions of wagmi and viem * bump common version * Bump versions for latest deps * Bump versions for pub * Version from wagmi to alpha flag * Revert testing ci changes * update CI to remove testing flow * Remove log * Remove capsule for failing build from demo * Fix wagmi versioning (#2206) * Add sunset warnings to tx preview (#2205) * Add sunset warnings to tx preview * Update versioning and merge in develop * Update wagmi usage docs (#2207) * Update wagmi usage docs * Refine example imports * Refine wagmi API * Refine docs, examples and use of wallet state to pass wagmiConnector * Merge in develop * Update wagmi docs * Fix - Core import of wagmi module version (#2210) * Update versions to publish with exact version of core * Yarn it * Update hw-wallet packages for type alignment (#2211) * Update packages for type alignment * Docs building again! * Update .github/workflows/docs.yml * Revert unnecessary change * Remove alpha.1 flags * Update versions for release * Update docs versions * Remove log
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. What is protestware?This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function. Consider that consuming this package my come along with functionality unrelated to its primary purpose. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
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.
✨ Highlights
📦 Changes per package
All
@web3-onboardpackages have been updated