[Snyk] Upgrade buefy from 0.9.8 to 0.9.29 #311
Conversation
This file contains hidden or 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
Snyk has created this PR to upgrade buefy from 0.9.8 to 0.9.29. See this package in npm: buefy See this project in Snyk: https://app.snyk.io/org/themodernpk/project/b403622b-450c-4350-b081-ce44ee09b702?utm_source=github&utm_medium=referral&page=upgrade-pr
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.
Snyk has created this PR to upgrade buefy from 0.9.8 to 0.9.29.
ℹ️ 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 21 versions ahead of your current version.
The recommended version was released 2 years ago.
Release notes
Package name: buefy
What's Changed in
v0.9.29Fixes
Tooltip- AbortController is not defined in SSR mode (Nuxt)Fieldwith bothgroupedandhorizontalpropstruegot a validation error. However, there is another issue that validation errors cannot be reset once they are set ifgroupedandhorizontalare combined (#4031).Full Changelog: v0.9.28...v0.9.29
0.9.28
What's Changed in
v0.9.28New features
isActiveDetailRowmethod in the default scoped slot props of table column (thanks @ OrestHk)activeevent emitted when dropdown turns active/inactive (thanks @ daniil4udo)Fixes
Fix #3961 Dropdown with "hover" trigger incorrectly rendered on mobile devices
Fix #3963 No dropdown showed up if the data array was empty and only the footer slot was registered (thanks @ GMartigny)
Fix #3971 Problems with table headers and dates due to 0.9.25 → 0.9.27 changes
Fix #3971 Percentage width on table columns doubly applied
Fix #3991 Potential call after unmount in the following components (thanks @ Arooba-git):
NumberInputSidebarFix #3991 Potential listener leaks in
SliderThumb(thanks @ Arooba-git)Fix #4000 Potential call after unmount in the following components (thanks @ Arooba-git):
AutocompleteColorpickerHSLRepresentationSquareColorpickerHSLRepresentationTriangleDropdownSliderTaginputTooltipRelease 0.9.28 by @ kikuomax in #4011
Full Changelog: v0.9.27...v0.9.28
What's Changed
/expoby @ wesdevpro in #3899build:scssscript by @ wesdevpro in #3913Buefy v0.9.26tonpmby @ wesdevpro in #3955v0.9.27by @ wesdevpro in #3959New Contributors
Full Changelog: v0.9.25...v0.9.27
What's Changed v0.9.25
New Contributors
Full Changelog: v0.9.24...v0.9.25
Added mobileModal to Clockpicker Component (#3840)
Added mobileModal to Clockpicker Component
Added mobileModal to Timepicker Component
Input-id prop checkbox
feat: 🎸 Adding a new prop to set the id for inner input
Adding a new prop to set the id for inner input for checkbox component
docs: ✏️ Adding helping data on checkbox api file
refactor: 💡 Changing prop name
Fix: Logo not displaying in the Sidebar documentation (#3838) (#3839)
Fix: Disabled radio button has cursor 'pointer' (#3826)
Fix: Sidebar image not displaying in the documentation (#3838)
Fix: Expired and broken websites in expo page (#3780) (#3845)
Number input null issue fix - #3698 (#3847)
number input value fix - #3698
checks fix
Co-authored-by: Amal Mathew [email protected]
Numberinput: fix long-press breaking when disabled (#3860)
Numberinput: fix long-press breaking when disabled
Numberinput: fix long-press unit test
Update notification.js (#3867)
Updated documentation for attribute
auto-closefrom #3855Fix: Full width sidebar doesn't have a close button (#3802) (#3856)
Fix: Expired and broken websites in expo page (#3780)
Fix: Full width sidebar doesn't have a close button (#3802)
Fix: Full width sidebar doesn't have a close button (#3802) - format code
Fix: Full width sidebar doesn't have a close button (#3802) - Add documentation
fix: infinite loop on Datepicker (#3877)
Datepickerended up with an infinite loop when auser tried to move focus onto an unselectable cell.
Bump Version From v0.9.23 to v0.9.24
Fix: Validation error on Input not reset by programmatically correcting the value (#3884) (#3886)
fix(lib): Input not validate on value prop change
Inputdid not validate an updated value ifvalueprop was updated from outside; i.e., without user interaction.Runs validation whenever
valueis changed from outside. Itdetermines the update is from outside if
computedValueand the newvalue are different. Intentionally uses
!=instead of!==, becausecomputedValueandvaluemay be either string or number.Introduces new test cases for
Inputthat test validation runs onrelevant events:
valueprop is programmatically changedAlso tests cases where the
Inputvalue has v-model binding. Thesetests make sure that the chain of events won't run validation twice on
the same value.
Fix: Validation error on Field with multiple child components (addons) persists after value is corrected (#3883) (#3885)
fix(lib): validation error on addons persisted
Fieldthat wraps multilechild components (has addons) persisted.
Fieldwraps its slot inanother
Field(wrapper) if the slot is consisting of multiplecomponents. It used to propagate
newTypeto the wrapper, but thisprevented the type of the wrapper updated once
newTypewas set dueto the line: https://github.com/buefy/buefy/blob/6f41e91bd24dfef8f680f27313e07b488ddcfc1d/src/utils/FormElementMixin.js#L137
Propagates
typeinstead ofnewTypeto the wrapper.Fieldthat tests ifFieldcontainingmultiple components (addons) reflects the validation status of a
wrapped input. This verifies the fix of the bug that
Fieldwithaddons did not update its validation status (
newType) once it wasset.
Add nearbyMonthDays prop support to Datetimepicker (#3881)
Add nearbyMonthDays prop support to Datetimepicker
Add Datepicker component prop
nearby-month-daysto Datetimepicker componentFIX lint Datetimepicker.vue
Use Datepicker default behavior for nearbyMonthDays prop
Update datetimepicker api doc with nearbyMonthDays prop
Update Twitter and Sponsor Links (#3888)
Updated The Documentation's Twitter Link
Updated Sponsor Links
Update FUNDING.yml
Update Package Json
Add Workflow to Publish Buefy on PR to Master
Co-authored-by: julzELO [email protected]
Co-authored-by: Aarón J. Montes [email protected]
Co-authored-by: Amal Mathew [email protected]
Co-authored-by: navedqb [email protected]
Co-authored-by: Sylvain Marty [email protected]
Co-authored-by: Kikuo Emoto [email protected]
Co-authored-by: Guillaume Mercey [email protected]
What's Changed