-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Build(deps): bump simple-icons from 5.2.0 to 5.3.0 #6662
Build(deps): bump simple-icons from 5.2.0 to 5.3.0 #6662
Conversation
There's arguably a case to be made that this constitutes a breaking change for our users in the sense that when we deploy this update existing users of the https://img.shields.io/badge/foo-bar-blue?logo=foursquare https://shields-staging-pr-6662.herokuapp.com/badge/foo-bar-blue?logo=foursquare https://shields-staging-pr-6662.herokuapp.com/badge/foo-bar-blue?logo=foursquare-city-guide I don't see any way around this outside waiting til SI v6 before pulling in any SI updates and doing our typical announcement about a major version upgrade, which doesn't seem remotely feasible nor does it really change the end result. I'd propose we carry on with this and maybe just add a discussion item or pinned issue detailing this with the reference to the city-guide slug for those that want to go back to the current icon |
Bumps [simple-icons](https://github.com/simple-icons/simple-icons) from 5.2.0 to 5.3.0. - [Release notes](https://github.com/simple-icons/simple-icons/releases) - [Commits](simple-icons/simple-icons@5.2.0...5.3.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
4e89555
to
0961d25
Compare
agreed 👍 |
Now simple-icons@5.4.0 released. Shall we upgrade simple-icons to 5.4.0 in this PR? |
Bumps simple-icons from 5.2.0 to 5.3.0.
Release notes
Sourced from simple-icons's releases.
Commits
2f86279
Release 12 new icons and 4 updated icons (v5.3.0)e8b25f9
version bump793d2b2
Update Foursquare & Add Foursquare City Guide (#5989)1537679
Add Zig programming language icon (#5572)7f7b53e
Added Polywork (#5806)3d1ee78
Update Beatport (#5985)645572a
Update Battle.net (#5986)fca0189
Add dbt icon (#5492)e2c6261
Update Grubhub (#5168)cb05549
Add ByteDance (#5909)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in the
.dependabot/config.yml
file in this repo: