Skip to content
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

release: 0.8.2 #563

Merged
merged 5 commits into from
Apr 22, 2024
Merged

release: 0.8.2 #563

merged 5 commits into from
Apr 22, 2024

Conversation

kanej
Copy link
Member

@kanej kanej commented Apr 22, 2024

0.8.2 - 2024-04-22

Added

  • Run Semantic Highlighting and document symbols on later solc versions not yet support by the Slang parser (behind feature flag) (562)

Xanewok and others added 5 commits April 18, 2024 15:18
This is arguably more useful approach - we designed our parser to be
error-tolerant and it makes more sense to offer slightly incomplete
experience rather than just suddenly turning off all features just
because the user is using a slightly newer version that may not get full
coverage.
feat: Use the latest version support by Slang even if not resolved
Update the package version and changelog for the `0.8.2 - 2024-04-22`
release.
Copy link

socket-security bot commented Apr 22, 2024

Copy link

socket-security bot commented Apr 22, 2024

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/keytar@7.9.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@kanej
Copy link
Member Author

kanej commented Apr 22, 2024

@SocketSecurity ignore npm/keytar@7.9.0

This was published 2 years ago. We get it via vsce - which we should probably update.

@kanej kanej merged commit 2618166 into main Apr 22, 2024
7 checks passed
@kanej kanej deleted the release/2024-04-22 branch April 22, 2024 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants