JoshuaKGoldberg / emoji-blast

Blasts emoji like fireworks all up in your HTML page. 🎆
https://emojiblast.dev
MIT License
244 stars 18 forks source link

chore(deps): update dependency lint-staged to v15.2.7 #430

Closed renovate[bot] closed 3 months ago

renovate[bot] commented 3 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 15.2.6 -> 15.2.7 age adoption passing confidence

Release Notes

okonet/lint-staged (lint-staged) ### [`v15.2.7`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1527) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.2.6...v15.2.7) ##### Patch Changes - [#​1440](https://togithub.com/lint-staged/lint-staged/pull/1440) [`a51be80`](https://togithub.com/lint-staged/lint-staged/commit/a51be804b63307ac7af3c82f4cb2d43dbe92daac) Thanks [@​iiroj](https://togithub.com/iiroj)! - In the previous version the native `git rev-parse --show-toplevel` command was taken into use for resolving the current git repo root. This version drops the `--path-format=absolute` option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading `git` to the latest version.

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.



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

vercel[bot] commented 3 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
emoji-blast ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 15, 2024 7:24pm
changeset-bot[bot] commented 3 months ago

⚠️ No Changeset found

Latest commit: f30a29371fc4cef07cd3becfe8a0363c11d3d151

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR