fix(deps): update internal dependencies #5084
Closed
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.
This PR contains the following updates:
1.28.0
->1.28.1
0.46.0
->0.55.0
4.0.0
->4.13.0
Release Notes
canonical/maas-react-components (@canonical/maas-react-components)
v1.28.1
Compare Source
Bug Fixes
canonical/react-components (@canonical/react-components)
v0.55.0
Compare Source
Features
v0.54.0
Compare Source
Features
v0.53.2
Compare Source
Bug Fixes
v0.53.1
Compare Source
Bug Fixes
v0.53.0
Compare Source
Features
v0.52.0
Compare Source
Features
v0.51.7
Compare Source
Bug Fixes
v0.51.6
Compare Source
Bug Fixes
v0.51.5
Compare Source
Bug Fixes
v0.51.4
Compare Source
Bug Fixes
v0.51.3
Compare Source
Bug Fixes
v0.51.2
Compare Source
Bug Fixes
v0.51.1
Compare Source
Bug Fixes
v0.51.0
Compare Source
Features
v0.50.6
Compare Source
Bug Fixes
v0.50.5
Compare Source
Bug Fixes
v0.50.4
Compare Source
Bug Fixes
v0.50.3
Compare Source
Bug Fixes
v0.50.2
Compare Source
Bug Fixes
v0.50.1
Compare Source
Bug Fixes
v0.50.0
Compare Source
Features
v0.49.0
Compare Source
Features
v0.48.0
Compare Source
Features
v0.47.4
Compare Source
Bug Fixes
v0.47.3
Compare Source
v0.47.3
🐛 Bug Fixes
v0.47.2
Compare Source
v0.47.2
🚀 Features
🔨 Maintenance
v0.47.1
Compare Source
v0.47.1
🔨 Maintenance
Full Changelog: canonical/react-components@v0.47.0...v0.47.1
v0.47.0
Compare Source
v0.46.1
What's Changed
scrollOverflow
prop toContextualMenu
to support scrolling the dropdown instead of overflowing the viewport (#961)🔨 Maintenance
Full Changelog: canonical/react-components@v0.46.0...v0.47.0
canonical/vanilla-framework (vanilla-framework)
v4.13.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.13.0
🚀 Features
🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
Full Changelog: canonical/vanilla-framework@v4.12.0...v4.13.0
v4.12.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.12.0
🚀 Features
🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.11.0...v4.12.0
v4.11.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.11.0
💣 Potentially breaking change
In #5081 we renamed the class names that add dividers to equal heights row component. If you've been using those already, rename them accordingly:
has-1st-divider
tohas-divider-1
, etc…🚀 Features
🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.10.0...v4.11.0
v4.10.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.10.0
💣 Breaking changes
Setting default theme via SCSS variables is now deprecated. For example, using
$theme-default-nav
with valuedark
will not work anymore. Useis-dark
oris-light
class names in HTML instead.🚀 Features
🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.9.1...v4.10.0
v4.9.1
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.9.1
🐛 Bug Fixes
🔨 Maintenance
Full Changelog: canonical/vanilla-framework@v4.9.0...v4.9.1
v4.9.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.9.0
🚀 Features
p-media-container
class by @petesfrench (#5012)🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.8.0...v4.9.0
v4.8.0
Compare Source
New in Vanilla v4.8.0
💅 New theming
This version introduces new theming system to Vanilla. Previous system was based on theme styling being applied on SCSS level on per-component basis. Newly introduced system utilises CSS custom properties to provide colour variables that are inherited through the whole document.
We currently support a light theme (default or via
is-light
class name) that features white background, paper theme (viais-paper
class) that uses new "paper" grey background that is used on most of our new designs, and dark theme (viais-dark
class) that is being used more often in recent designs to highlight some significant pages.🚧 Work in progress
Current release of Vanilla 4.8.0 contains the foundation work of this new theming and includes migration of most commonly used themed components. The work is not complete yet, there are still components that use the old theming system and many components not themed at all. We will continue to migrate remaining parts in upcoming versions.
We tried to make sure to keep this change backwards compatible, so hopefully it should not affect styling of existing components in any significant and unexpected way.
🎨 Default icon colour
As part of the theming we improved consistency of colours we use across themes. As a result of that the default colour of most of Vanilla icons (in default light theme) was changed to be the same as text colour (black
#000
) instead of previous value of$color-mid-dark
(#666
). If you are using any custom icons this may cause inconsistencies.For consistency with Vanilla use built-in icons, or update your icons to use
$colors--light-theme--icon
(or$colors--dark-theme--icon
), depending on the theme.🏗️ New and deprecated components
Alongside the theming work, we are also providing components to help build page sections in the new branding style, and deprecating some old components to avoid confusion.
New components include the hero section and new Suru sections, that should simplify building of the hero sections on the pages.
We also deprecated a variety of legacy strip variants, reducing the options and updating the strip component to utilise new theming.
For more details check the changelog in our documentation.
💣 Breaking changes
The (now deprecated) inverted link component was updated to support new theming. This may cause an issue that inverted link turns black when used in default "light" theme. Please add
is-dark
class name for any element that changes background to dark, so that the child components would correctly inherit the theme.🙋 Guest devs
Vanilla team was joined for a Pulse by wonderful guest developers: @britneywwc @chillkang. This release would not be possible without their contributions. Thanks!
📋 Changelog
🚀 Features
🐛 Bug Fixes
🔨 Maintenance
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New Contributors
Full Changelog: canonical/vanilla-framework@v4.7.0...v4.8.0
v4.7.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.7.0
🚀 Features
💣 Potentially breaking changes
Updates to top navigation (increased padding and new 25/75 layout variant) may cause top navigation items not fit on smaller screens. If your project adjusts
$breakpoint-navigation-threshold
you may need to update its value, so that navigation switches to mobile view when items don't fit anymore.🐛 Bug Fixes
🔨 Maintenance
Full Changelog: canonical/vanilla-framework@v4.6.0...v4.7.0
v4.6.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.6.0
🚀 Features
💣 Potentially breaking changes
With the introduction of new responsive grid patterns (
row--25-75-on-medium
, etc), the default responsive behaviour ofrow--25-75
has changed. Previously on medium screens it did not split the layout, but used a stacked mobile layout. With Vanilla 4.6.0 therow--25-75
will split into 2+4 columns layout on medium screens by default. This also means thatis-split-on-medium
modifier class is no longer needed, as its behaviour is now default forrow--25-75
.If you are using
row--25-75
withoutis-split-on-medium
make sure that the layout doesn't break on medium screen sizes.If you are using
row--25-75
withis-split-on-medium
no change is needed, butis-split-on-medium
is redundant and can be safely removed from code.For more information refer to the Vanilla grid documentation.
🐛 Bug Fixes
🔨 Maintenance
Full Changelog: canonical/vanilla-framework@v4.5.1...v4.6.0
v4.5.1
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.5.1
🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.5.0...v4.5.1
v4.5.0
Compare Source
Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
New in Vanilla v4.5.0
🚀 Features
📝 Documentation
New Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.