-
Notifications
You must be signed in to change notification settings - Fork 28
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
fix(deps): update all non-major dependencies #330
Merged
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
9f7319d
to
37b0333
Compare
000ab0a
to
f9a8b71
Compare
49f765d
to
a2c5424
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
a2c5424
to
c4e42d4
Compare
BethGriggs
approved these changes
Jul 22, 2024
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BethGriggs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
rm3l
added a commit
to rm3l/janus-idp.github.io
that referenced
this pull request
Jul 23, 2024
Not sure why we are building the website from PRs in the backstage-plugins repo, but PR checks in the janus-idp/backstage-plugins repo are failing due to an error about dirty workspaces. See [1]. This has been narrowed down to the bump of Husky to v9.1.1 [2], which, according to the release notes [3], makes Husky automatically remove some deprecated statements. [1] https://github.com/janus-idp/backstage-plugins/actions/workflows/pr-website.yaml [2] janus-idp#330 [3] https://github.com/typicode/husky/releases/tag/v9.1.1
3 tasks
openshift-merge-bot bot
pushed a commit
that referenced
this pull request
Jul 23, 2024
Not sure why we are building the website from PRs in the backstage-plugins repo, but PR checks in the janus-idp/backstage-plugins repo are failing due to an error about dirty workspaces. See [1]. This has been narrowed down to the bump of Husky to v9.1.1 [2], which, according to the release notes [3], makes Husky automatically remove some deprecated statements. [1] https://github.com/janus-idp/backstage-plugins/actions/workflows/pr-website.yaml [2] #330 [3] https://github.com/typicode/husky/releases/tag/v9.1.1
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:
1.72.0
->1.72.1
20.14.10
->20.14.11
11.3.4
->11.3.8
9.0.11
->9.1.1
2.0.6
->2.0.9
Release Notes
segmentio/analytics-next (@segment/analytics-next)
v1.72.1
Compare Source
Patch Changes
73ac593
Thanks @silesky! - Update argument resolver to user interface rather than full Userframer/motion (framer-motion)
v11.3.8
Compare Source
Changed
v11.3.7
Compare Source
Changed
Set
lookups.v11.3.6
Compare Source
Changed
v11.3.5
Compare Source
Fixed
react
andreact-dom
as dependencies.typicode/husky (husky)
v9.1.1
Compare Source
v9.1.0
Compare Source
Super saiyan
goddog! It's over 9.0.0!There's a bug with this release which prevents the deprecation notice to appear and requires to remove
#!/usr/bin/env sh
and. "$(dirname -- "$0")/_/husky.sh"
(which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.What's new
You can now run package commands directly, no need for
npx
or equivalents.It makes writing hooks more intuitive and is also slightly faster 🐺⚡️
A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.
For more advanced use cases, see lint-staged.
Fixes
bunx husky init
commandDeprecations
#!/usr/bin/env sh
and. "$(dirname -- "$0")/_/husky.sh"
from your hooks~/.huskyrc
to.config/husky/init.sh
Support for these will be removed in v10, notices have been added.
Friendly reminder
If Git hooks don't fit your workflow, you can disable Husky globally. Just add
export HUSKY=0
to.config/husky/init.sh
.I've seen some confusion about this on X, so just a heads-up!
Sponsoring
Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.
Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉
vercel/turbo (turbo)
v2.0.9
Compare Source
v2.0.8
: Turborepo v2.0.8Compare Source
What's Changed
Examples
Changelog
Full Changelog: vercel/turborepo@v2.0.7...v2.0.8
v2.0.7
: Turborepo v2.0.7Compare Source
What's Changed
Examples
with-nestjs
example by @Neosoulink in https://github.com/vercel/turbo/pull/8162Changelog
--output-logs
andoutputLogs
for persisting logs after TUI exits by @chris-olszewski in https://github.com/vercel/turbo/pull/8612Opts
fromConfig
by @NicholasLYang in https://github.com/vercel/turbo/pull/8759New Contributors
Full Changelog: vercel/turborepo@v2.0.6...v2.0.7
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 is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.