Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency vanilla-framework to v4.9.0 - autoclosed #1035

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vanilla-framework (source) 4.6.0 -> 4.9.0 age adoption passing confidence

Release Notes

canonical/vanilla-framework (vanilla-framework)

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
🐛 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 (via is-paper class) that uses new "paper" grey background that is used on most of our new designs, and dark theme (via is-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.

🙋 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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@webteam-app
Copy link

Demo starting at https://react-components-1035.demos.haus

@renovate renovate bot force-pushed the renovate/internal branch 5 times, most recently from dc87901 to 54ac5b4 Compare February 8, 2024 08:58
@renovate renovate bot changed the title chore(deps): update dependency vanilla-framework to v4.7.0 chore(deps): update dependency vanilla-framework to v4.8.0 Feb 16, 2024
@renovate renovate bot force-pushed the renovate/internal branch 2 times, most recently from 0263df6 to 2e8bd59 Compare February 21, 2024 11:53
@renovate renovate bot force-pushed the renovate/internal branch 4 times, most recently from 82ccbbb to 0fa63bb Compare March 6, 2024 15:14
@renovate renovate bot changed the title chore(deps): update dependency vanilla-framework to v4.8.0 chore(deps): update dependency vanilla-framework to v4.9.0 Mar 14, 2024
@renovate renovate bot changed the title chore(deps): update dependency vanilla-framework to v4.9.0 chore(deps): update dependency vanilla-framework to v4.9.0 - autoclosed Mar 19, 2024
@renovate renovate bot closed this Mar 19, 2024
@renovate renovate bot deleted the renovate/internal branch March 19, 2024 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant