Update dependency vanilla-framework to v4.9.0 - autoclosed #270
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Demo starting at https://global-nav-270.demos.haus |
renovate
bot
force-pushed
the
renovate/internal
branch
from
1d11c42
to
5b8c6d4
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/internal
branch
from
5b8c6d4
to
4fcc1fd
Compare
renovate
bot
force-pushed
the
renovate/internal
branch
from
4fcc1fd
to
607144c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/internal
branch
2 times, most recently
from
718d5c5
to
02eebd4
Compare
renovate
bot
force-pushed
the
renovate/internal
branch
from
02eebd4
to
bbca54c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/internal
branch
2 times, most recently
from
90cecce
to
40a01ea
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/internal
branch
3 times, most recently
from
beaafd2
to
1adb245
Compare
renovate
bot
force-pushed
the
renovate/internal
branch
from
1adb245
to
16023fc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/internal
branch
from
16023fc
to
eb02c47
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/internal
branch
from
eb02c47
to
e4865d9
Compare
renovate
bot
force-pushed
the
renovate/internal
branch
from
e4865d9
to
44c459e
Compare
renovate
bot
changed the title
renovate
bot
changed the title
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.
This PR contains the following updates:
4.0.0->4.9.0Release Notes
canonical/vanilla-framework (vanilla-framework)
v4.9.0Compare 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-containerclass by @petesfrench (#5012)🐛 Bug Fixes
📝 Documentation
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.8.0...v4.9.0
v4.8.0Compare 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-lightclass name) that features white background, paper theme (viais-paperclass) that uses new "paper" grey background that is used on most of our new designs, and dark theme (viais-darkclass) 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.
🙋 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.0Compare 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-thresholdyou 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.0Compare 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-75has changed. Previously on medium screens it did not split the layout, but used a stacked mobile layout. With Vanilla 4.6.0 therow--25-75will split into 2+4 columns layout on medium screens by default. This also means thatis-split-on-mediummodifier class is no longer needed, as its behaviour is now default forrow--25-75.If you are using
row--25-75withoutis-split-on-mediummake sure that the layout doesn't break on medium screen sizes.If you are using
row--25-75withis-split-on-mediumno change is needed, butis-split-on-mediumis 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.1Compare 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.0Compare 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
Full Changelog: canonical/vanilla-framework@v4.4.0...v4.5.0
v4.4.0Compare 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.4.0
🚀 Features
🐛 Bug Fixes
🔨 Maintenance
Full Changelog: canonical/vanilla-framework@v4.3.0...v4.4.0
v4.3.0Compare 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.3.0
💣 Fixing misaligned logo sections from 4.2
In Vanilla 4.2 we reworked our logo section component. If used correctly, with correctly sized images it should be a seamless upgrade, but if you have used logo section with logos not correctly spaced by visual design team you may end up with broken look of oversized logos.
In Vanilla 4.3 we introduced a fallback workaround for this regression. It doesn't fix the issue automatically, but we introduced a
has-misaligned-imagesfallback class name that can be added to broken logo sections if logo images can't be replaced by new ones. You can learn more in the docs.🚀 Features
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.2.0...v4.3.0
v4.2.0Compare 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.2.0
💣 Potentially breaking changes
In Vanilla 4.2 we reworked our logo section component. If used correctly, with correctly sized images it should be a seamless upgrade, but if you have used logo section with logos not correctly spaced by visual design team you may end up with broken look of oversized logos.
🚀 Features
🐛 Bug Fixes
🔨 Maintenance
New Contributors
Full Changelog: canonical/vanilla-framework@v4.1.0...v4.2.0
v4.1.0Compare 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.1.0
🚀 Features
📝 Documentation
🔨 Maintenance
Full Changelog: canonical/vanilla-framework@v4.0.0...v4.1.0
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.