Skip to content

[Snyk] Upgrade prettier-plugin-solidity from 1.0.0-beta.19 to 1.1.3 #27

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.

Sign up for GitHub

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

Jump to bottom
Merged
Woodpile37 merged 2 commits into from
Aug 17, 2023
Merged

[Snyk] Upgrade prettier-plugin-solidity from 1.0.0-beta.19 to 1.1.3 #27

Woodpile37 merged 2 commits into from
Aug 17, 2023

Conversation

@snyk-bot
Copy link

@snyk-bot snyk-bot commented Mar 27, 2023

Snyk has created this PR to upgrade prettier-plugin-solidity from 1.0.0-beta.19 to 1.1.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 12 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-03-01.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Prototype Pollution
SNYK-JS-UNSETVALUE-2400660		 375/1000
Why? CVSS 7.5		 No Known Exploit
Prototype Pollution
SNYK-JS-Y18N-1021887		 375/1000
Why? CVSS 7.5		 Proof of Concept
Prototype Poisoning
SNYK-JS-QS-3153490		 375/1000
Why? CVSS 7.5		 Proof of Concept
Prototype Pollution
SNYK-JS-JSON5-3182856		 375/1000
Why? CVSS 7.5		 Proof of Concept
Denial of Service (DoS)
npm:mem:20180117		 375/1000
Why? CVSS 7.5		 No Known Exploit
Cryptographic Issues
SNYK-JS-ELLIPTIC-1064899		 375/1000
Why? CVSS 7.5		 No Known Exploit
Regular Expression Denial of Service (ReDoS)
SNYK-JS-GLOBPARENT-1016905		 375/1000
Why? CVSS 7.5		 Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-HIGHLIGHTJS-1048676		 375/1000
Why? CVSS 7.5		 No Known Exploit
Authentication Bypass
SNYK-JS-HTTPAUTH-471683		 375/1000
Why? CVSS 7.5		 No Known Exploit
Prototype Pollution
SNYK-JS-JSON5-3182856		 375/1000
Why? CVSS 7.5		 Proof of Concept
Prototype Pollution
SNYK-JS-JSON5-3182856		 375/1000
Why? CVSS 7.5		 Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-UGLIFYJS-1727251		 375/1000
Why? CVSS 7.5		 No Known Exploit
Arbitrary Code Injection
SNYK-JS-UNDERSCORE-1080984		 375/1000
Why? CVSS 7.5		 Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: prettier-plugin-solidity
  • 1.1.3 - 2023-03-01

    This version adds support for user-defined operators, a feature introduced in Solidity 0.8.19.

  • 1.1.2 - 2023-02-06

    This version adds support for named parameters in mappings, introduced in Solidity 0.8.18. This means you can add names to your mappings parameters:

    mapping(address account => uint balance) balanceOf;

    and Prettier Solidity will format it correctly.

    Thanks to @ zemse for working on this!

  • 1.1.1 - 2022-12-29

    With this version we started supporting prettier V3 which at the moment it's in their 3.0.0-alpha.4 version. (#757)

    Some internal tweaks and removed some dependencies that were no longer used. (thanks to @ frangio for noticing #780)

  • 1.1.0 - 2022-12-13

    With this version, we are releasing a standalone build (#727).
    It follows the same patterns Prettier uses for their internal plugins such as UMD.
    Hopefully this will make integration for projects based on the browser easy and will be automatically shipped on each release to http://unpkg.com/prettier-plugin-solidity@latest.

    We also took care of a small bug that would print an extra line when formatting solidity code within a markdown code block (#765).

  • 1.0.0 - 2022-11-17

    We are happy to release the first stable version of Prettier Solidity! 🎉 🎉

    What does this mean for you as a user? Semantic versioning doesn't make a lot of sense for a formatter, so it's hard to give hard rules about what will be the meaning of future versions. But we'll try to follow these guidelines:

    • We won't make big formatting changes within the same major version. For example, you shouldn't get all your function signatures changed just because you upgraded to, say, v1.1.0.
    • We won't remove any option within the same major version.
    • We'll use patch versions (e.g., moving from 1.2.3 to 1.2.4) for bug fixes and very minor formatting changes.
    • We'll use minor versions (e.g., moving from 1.2.3 to 1.3.0) for new language constructs, new options (if any) and somewhat bigger formatting changes.

    What separates a "very minor formatting change" from a "bigger one" is hard to define precisely, of course, so some of these decisions will be very subjective, but we'll try to do our best.

    Thanks for using our plugin and remember to star the repo! ⭐

  • 1.0.0-rc.1 - 2022-11-02

    This is our first release candidate for a stable v1.0.0!

    This version includes some significant changes:

    • We removed the explicitTypes option, since we believe that this belongs to a linter. The behavior now is the same one that you would get if using explicitTypes: "preserve", meaning that we'll never convert an uint to an uint256 or vice versa.
    • In previous versions, the parameters of a function definition would always be split if there were more than two of them. Starting now, we only split them if the line doesn't fit in line-width. Plus, the way this works is that first the parameters are split, then the modifiers (if they also don't fit in a single line), and finally the return parameters (also only if they don't fit).
    • The exponentiation operator (**) now has spaces around it. This is more consistent with other operators, and it looks better for long variable names (that is, base ** decimals is better than base**decimals). We do know that this is not as nice for some cases (2 ** 10), but we are erring on the side of consistency and a better worst-case scenario.

    As an example, a function like this:

    contract Foo {
  function f(uint x, uint y, uint z) mod1 mod2 { x**y**z; }
}

    would be formatted in the previous version like this:

    contract Foo {
    function f(
        uint256 x,
        uint256 y,
        uint256 z
    ) mod1 mod2 {
        x**y**z;
    }
}

    and now it will be formatted like this:

    contract Foo {
    function f(uint x, uint y, uint z) mod1 mod2 {
        x ** y ** z;
    }
}

    Please upgrade to the latest version and let us if you find any issues!

  • 1.0.0-dev.24 - 2022-10-19
  • 1.0.0-dev.23 - 2022-07-15
  • 1.0.0-dev.22 - 2022-07-11

    This new release provides some bug fixes and new formatting added by solidity.

    #643
    #683
    #685
    #693
    #694

  • 1.0.0-dev.21 - 2022-02-10
  • 1.0.0-beta.24 - 2022-08-06

    Bump to beta.24

  • 1.0.0-beta.20 - 2022-02-10
  • 1.0.0-beta.19 - 2021-11-11

    Changes in this version:

    • 🔧 node 12 is no longer supported. #598 thanks @ mattiaerre
    • 🐛 fixed bug for pragma statements containing multiple versions. #583 thanks @ fvictorio
    • ✨ added support for user defined types. #607 thanks @ zemse
from prettier-plugin-solidity GitHub release notes
Commit messages
Package name: prettier-plugin-solidity

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@changeset-bot
Copy link

changeset-bot bot commented Aug 17, 2023

⚠️ No Changeset found

Latest commit: 29c3521

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Woodpile37 Woodpile37 merged commit d8262e9 into release-v4.5 Aug 17, 2023
@Woodpile37 Woodpile37 mentioned this pull request Aug 17, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@snyk-bot @Woodpile37