-
Notifications
You must be signed in to change notification settings - Fork 1
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 all dependencies - autoclosed #45
Closed
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/all
branch
from
January 26, 2024 11:32
8f9ea71
to
c379e40
Compare
Deploying with Cloudflare Pages
|
renovate
bot
changed the title
chore(deps): update actions/cache action to v4
fix(deps): update all dependencies
Jan 26, 2024
renovate
bot
force-pushed
the
renovate/all
branch
from
January 26, 2024 16:10
c379e40
to
9bd4dc8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 28, 2024 05:53
9bd4dc8
to
9073848
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 28, 2024 13:41
9073848
to
fadd61f
Compare
renovate
bot
changed the title
fix(deps): update all dependencies
chore(deps): update all dependencies
Jan 28, 2024
renovate
bot
force-pushed
the
renovate/all
branch
from
January 28, 2024 22:34
fadd61f
to
5e7fea6
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 29, 2024 03:03
5e7fea6
to
8ff595b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 29, 2024 06:14
8ff595b
to
4031cf0
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 30, 2024 19:40
4031cf0
to
94a0ead
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 31, 2024 10:27
94a0ead
to
2f47ad4
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 31, 2024 20:08
2f47ad4
to
c43aa73
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 1, 2024 15:39
c43aa73
to
c8ed971
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 2, 2024 20:13
c8ed971
to
119c8e7
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 3, 2024 04:59
119c8e7
to
2e732e3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 3, 2024 10:21
2e732e3
to
16d149c
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 3, 2024 20:20
16d149c
to
af749bb
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 4, 2024 07:28
af749bb
to
61d4407
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 6, 2024 00:57
61d4407
to
ff30df0
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 7, 2024 06:32
ff30df0
to
79ab949
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
February 8, 2024 06:47
79ab949
to
02874ee
Compare
renovate
bot
changed the title
chore(deps): update all dependencies
chore(deps): update all dependencies - autoclosed
Feb 8, 2024
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:
18.5.0
->18.6.0
18.5.0
->18.6.0
^0.0.40
->^0.0.43
20.11.6
->20.11.16
18.2.48
->18.2.53
18.2.55
(+1)v3
->v4
5.13.1
->5.13.3
5.13.0
->5.13.1
3.13.0
->3.13.1
5.13.0
->5.13.1
6.13.0
->6.13.1
5.13.0
->5.13.1
6.13.0
->6.13.1
8.13.0
->8.13.1
5.13.0
->5.13.1
5.13.0
->5.13.1
^8.0.3
->^9.0.0
15.2.0
->15.2.1
15.2.2
3.2.4
->3.2.5
Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v18.6.0
Compare Source
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v18.6.0
Compare Source
Features
studio-freight/lenis (@studio-freight/react-lenis)
v0.0.43
Compare Source
v0.0.42
Compare Source
actions/cache (actions/cache)
v4
Compare Source
gatsbyjs/gatsby (gatsby)
v5.13.3
Compare Source
v5.13.2
Compare Source
gatsbyjs/gatsby (gatsby-plugin-google-gtag)
v5.13.1
Compare Source
Note: Version bump only for package gatsby-plugin-google-gtag
gatsbyjs/gatsby (gatsby-plugin-image)
v3.13.1
Compare Source
Note: Version bump only for package gatsby-plugin-image
gatsbyjs/gatsby (gatsby-plugin-manifest)
v5.13.1
Compare Source
Note: Version bump only for package gatsby-plugin-manifest
gatsbyjs/gatsby (gatsby-plugin-offline)
v6.13.1
Compare Source
Note: Version bump only for package gatsby-plugin-offline
gatsbyjs/gatsby (gatsby-plugin-sharp)
v5.13.1
Compare Source
Note: Version bump only for package gatsby-plugin-sharp
gatsbyjs/gatsby (gatsby-plugin-sitemap)
v6.13.1
Compare Source
Note: Version bump only for package gatsby-plugin-sitemap
gatsbyjs/gatsby (gatsby-source-contentful)
v8.13.1
Compare Source
Note: Version bump only for package gatsby-source-contentful
gatsbyjs/gatsby (gatsby-source-filesystem)
v5.13.1
Compare Source
Note: Version bump only for package gatsby-source-filesystem
gatsbyjs/gatsby (gatsby-transformer-sharp)
v5.13.1
Compare Source
Note: Version bump only for package gatsby-transformer-sharp
typicode/husky (husky)
v9.0.10
Compare Source
v9.0.9
Compare Source
v9.0.8
Compare Source
v9.0.7
Compare Source
~/.huskyrc
correctly (compatibility with v8)v9.0.6
Compare Source
v9.0.5
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.0.1...v9.0.2
v9.0.1
Compare Source
Kicking off the year with an exciting update!
TLDR;
Improved user experience and a (even) smaller package size while packing in more features!
👋 By the Way
I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂
Introducing
husky init
Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.
v8
v9
Adding a New Hook
Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic
echo
command.v8
v9
Further Size Reduction
v8
was already the most compact Git hooks manager at approximately6kB
.v9
takes this a step further, reducing the size to just3kB
, likely making it the smallest devDependency in your toolkit.To give you an idea of how small it is, the biggest file in the project is the MIT license 😄
More to Come
Additional features are in the pipeline for
v9
. Stay tuned 🙌Other Changes
--provenance
for safer publishing.$XDG_CONFIG_HOME
support. Move~/.huskyrc
to~/.config/husky/init.sh
for centralized configuration.husky install
. Usehusky
orhusky some/dir
for the same functionality (deprecation notice to be added)..git
is missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1
withHUSKY=2
for debugging.ESM
for module usage.How to Migrate
v9
is backward compatible withv8
, allowing you to freely upgrade and migrate your hooks later.package.json
.husky/pre-commit
okonet/lint-staged (lint-staged)
v15.2.1
Compare Source
Patch Changes
e4023f6
Thanks @iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.prettier/prettier (prettier)
v3.2.5
Compare Source
diff
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
Use
"json"
parser fortsconfig.json
by default (#16012 by @sosukesuzuki)In v2.3.0, we introduced
"jsonc"
parser which adds trialing comma by default.When adding a new parser we also define how it will be used based on the
linguist-languages
data.tsconfig.json
is a special file used by TypeScript, it uses.json
file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing.json
file extension.We decide to treat it as a JSON file for now to avoid the extra configuration step.
To keep using the
"jsonc"
parser for yourtsconfig.json
files, add the following to your.pretterrc
fileConfiguration
📅 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 becomes conflicted, 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.