-
-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: version package #925
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: viem@1.4.0 |
🚨 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. 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
|
77f079a
to
c9e3f2b
Compare
c9e3f2b
to
cb93a5e
Compare
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
viem@1.4.1
Patch Changes
789592dc
Thanks @jxom! - Fixed an issue where callingencodePacked
with an emptybytes[]
array would return anUint8Array
instead ofHex
value.#922
71c9c933
Thanks @mikemcdonald! - Fixed an issue whereparseUnits
would throwCannot convert to a BigInt
for large numbers with a fraction component.PR-Codex overview
This PR focuses on releasing version 1.4.1 of the "viem" package.
Detailed summary
encodePacked
with an emptybytes[]
array would return anUint8Array
instead ofHex
value. (Commit:789592dc
, Thanks @jxom)parseUnits
would throwCannot convert to a BigInt
for large numbers with a fraction component. (Pull Request: #922, Commit:71c9c933
, Thanks @mikemcdonald)