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.6.0 #1015

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2024

Mend Renovate

This PR contains the following updates:

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

Release Notes

canonical/vanilla-framework (vanilla-framework)

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 of row--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 the row--25-75 will split into 2+4 columns layout on medium screens by default. This also means that is-split-on-medium modifier class is no longer needed, as its behaviour is now default for row--25-75.

If you are using row--25-75 without is-split-on-medium make sure that the layout doesn't break on medium screen sizes.
If you are using row--25-75 with is-split-on-medium no change is needed, but is-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


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-1015.demos.haus

@renovate renovate bot force-pushed the renovate/internal branch 6 times, most recently from ad93f1d to 4254bbf Compare January 19, 2024 10:46
@renovate renovate bot force-pushed the renovate/internal branch from 4254bbf to 9ce1e61 Compare January 19, 2024 10:47
@mas-who mas-who merged commit a2cca25 into main Jan 19, 2024
7 checks passed
@renovate renovate bot deleted the renovate/internal branch January 19, 2024 11:00
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.

2 participants