-
Notifications
You must be signed in to change notification settings - Fork 803
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
Lock file maintenance #31769
Lock file maintenance #31769
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The node downgrades look weird, but everything else seems like minor dependency bumps.
pnpm-lock.yaml
Outdated
dev: true | ||
|
||
/@types/glob@8.1.0: | ||
resolution: {integrity: sha512-IO+MJPVhoqz+28h1qLAcBEH2+xHMK6MTyHJc7MTnnYb6wsoLR29POVGJ7LycmVXIqyy/4/2ShP5sUwTXuOwb/w==} | ||
dependencies: | ||
'@types/minimatch': 5.1.2 | ||
'@types/node': 20.3.1 | ||
'@types/node': 16.18.38 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird node downgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not exactly a node downgrade, just a downgrade on the package that tells typescript about types for node builtins.
I'm guessing it decided to downgrade because the only dep on this comes via @storybook/core-common
→ glob-promise
→ @types/glob
, and @storybook/core-common
depends on @types/node
^16.0.0, so the deduplication logic decided it may as well have just one version of @types/node
in the tree rather than two. But why it decided to do that now rather than last month I have no idea.
pnpm-lock.yaml
Outdated
@@ -9906,16 +9969,16 @@ packages: | |||
/@types/node-fetch@2.6.4: | |||
resolution: {integrity: sha512-1ZX9fcN4Rvkvgv4E6PAY5WXUFWFcRWxZa3EW83UjycOB9ljJCedb2CupIP4RZMEwF/M3eTcCihbBRgwtGbg5Rg==} | |||
dependencies: | |||
'@types/node': 20.3.1 | |||
'@types/node': 16.18.38 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another weird node downgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to the above.
Artifact update problem seems to be an issue with |
Whee. Called it last month: #31308 (comment) |
57cb30e
to
577003c
Compare
Apparently the return types of `setTimeout()` and `setInterval()` depend on the environment, in browsers they're numbers while in node they're `Timeout` and `Timer`. I have no idea why, but some update here (assocated with the "expect" package?) makes tsc suddenly start complaining about this. Some quick searching suggests that the way to do this is to either remove the type declarations or do like `ReturnType< typeof setTimeout >` to let typescript figure it out. I went with the latter, since someone felt that declaring the type here in the first place was a good idea. But to make *that* work, we also need to rename the `ReturnType` type variable to something else so it doesn't mask TypeScript's built-in `ReturnType<>` utility type. Whee.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is happy, and a JN site seems to work too
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: Branch creation - "before 3:00 am on Monday on the 7th through 13th day of the month" in timezone UTC, 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 Renovate Bot.