[Snyk] Upgrade vuetify from 1.5.4 to 2.1.12 #9
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.
Snyk has created this PR to upgrade vuetify from 1.5.4 to 2.1.12.
ℹ️ 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.Warning: This is a major version upgrade, and may be a breaking change.
The recommended version fixes:
SNYK-JS-VUETIFY-474604
Release notes
Package name: vuetify
🔧 Bug Fixes
🔧 Bug Fixes
🔧 Bug Fixes
closes #9364
closes #9472
Reverts
If you get infinite recursion errors in a dialog, add
:retain-focus="false"
🔧 Bug Fixes
A low impact security vulnerability was identified with the
v-messages
component. Using the value prop, it was possible to perform an XSS attack.NOTICE
If you are not using HTML for the props rules, messages, hint, success-messages or error-messages, you do not need to do anything.
All values for
v-message
are now escaped. This primarily affects inputs as they usev-message
for rule and hint output. To accommodate this change, a scoped slot has been added for users whoneed to customize the styling of messages as they will no longer render html.
Components this fix impacts:
v-autocomplete
v-checkbox
v-combobox
v-file-input
v-input
v-messages
v-overflow-btn
v-radio-group
v-select
v-slider
v-switch
v-textarea
v-text-field
If you have any questions, please reach out to us in our community, https://community.vuetifyjs.com
🔧 Bug Fixes
NOTICE
A snafu with cherry-picking caused the previous security fix to not make it in. Please see https://github.com/vuetifyjs/vuetify/releases/tag/v2.1.9
🔧 Bug Fixes
🔧 Bug Fixes
🔧 Bug Fixes
🔧 Bug Fixes
🔧 Bug Fixes
A low impact security vulnerability was identified with the
v-messages
component. Using the value prop, it was possible to perform an XSS attack.NOTICE
If you are not using HTML for the props rules, messages, hint, success-messages or error-messages, you do not need to do anything.
All values for
v-message
are now escaped. This primarily affects inputs as they usev-message
for rule and hint output. To accommodate this change, a scoped slot has been added for users whoneed to customize the styling of messages as they will no longer render html.
Components this fix impacts:
v-autocomplete
v-checkbox
v-combobox
v-file-input
v-input
v-messages
v-overflow-btn
v-radio-group
v-select
v-slider
v-switch
v-textarea
v-text-field
If you have any questions, please reach out to us in our community, https://community.vuetifyjs.com
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