Update dependency vanilla-framework to v4 #1632
Merged
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://charmhub-io-1632.demos.haus |
Codecov Report
@@ Coverage Diff @@
## main #1632 +/- ##
==========================================
- Coverage 40.87% 40.69% -0.19%
==========================================
Files 20 20
Lines 1661 1661
==========================================
- Hits 679 676 -3
- Misses 982 985 +3
Flags with carried forward coverage won't be shown. Click here to find out more. |
renovate
bot
force-pushed
the
renovate/major-internal
branch
from
b0ab404
to
0bba248
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-internal
branch
2 times, most recently
from
23978a8
to
a7f0666
Compare
renovate
bot
force-pushed
the
renovate/major-internal
branch
from
a7f0666
to
2b6f9f3
Compare
renovate
bot
force-pushed
the
renovate/major-internal
branch
from
2b6f9f3
to
70c02f6
Compare
steverydz
approved these changes
Oct 12, 2023
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:
3.15.1->4.4.0Release Notes
canonical/vanilla-framework (vanilla-framework)
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
v4.0.0Compare Source
🍦 New in Vanilla 4.0
Vanilla 4.0 introduces elements of new style used for current rebranding of Canonical's brochure websites, including typography changes (utilising new variable Ubuntu font), wider grid width, some updated colours, and updates to any related components.
The most important changes include:
🚀 Migrating to Vanilla 4.0
We treat Vanilla 4.0 as an interim release that includes elements of new branding, but keep the support for old style of components as well to allow for easier and more granular migration on our biggest websites. Therefore, there are no significant breaking changes or removed components.
But because of quite significant visual changes introduced by updated typography and wider grid, it is recommended to properly QA templates and pages, especially if there are any custom styles built on top of Vanilla.
You can check our migration guide for more details.
🔗 Getting Vanilla Framework
Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs
📝 Change log
Full Changelog: canonical/vanilla-framework@v3.15.1...v4.0.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.