chore(deps): pin dependencies - autoclosed - #206
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 25, 2026 03:56
a0d0a25 to
8039092
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 25, 2026 04:24
8039092 to
0739346
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 25, 2026 21:35
0739346 to
24f3251
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 25, 2026 22:24
24f3251 to
795af5f
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 26, 2026 00:58
795af5f to
2f2d215
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 26, 2026 15:38
2f2d215 to
f272576
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 26, 2026 23:11
f272576 to
4b28777
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 27, 2026 03:34
4b28777 to
9099352
Compare
|
Deployment failed for project careerrat-website with the following error: Learn More: https://vercel.com/codeswhat?upgradeToPro=build-rate-limit |
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
2 times, most recently
from
August 27, 2026 05:49
0bb2968 to
270e28b
Compare
scttbnsn
added a commit
that referenced
this pull request
Aug 27, 2026
#241) Four of careerrat's six CI failures since 08-20 are one cause. `npm ci` died with a misleading `EUSAGE: can only install with an existing package-lock.json` on #206 and #208 while the lockfile was plainly committed. The real error only appears when you run what Renovate runs: npm error code EOVERRIDE npm error Override for sharp@0.35.3 conflicts with direct dependency `overrides.sharp` was a literal `^0.35.0` while `sharp` is also a root devDependency. Pinning the direct dep made the two specs diverge, npm refused to regenerate the lockfile, `renovate/artifacts` went red, and Renovate pushed the package.json change anyway. CI then met a package.json and a lockfile that disagree, which npm 11 reports as a *missing* lockfile rather than a stale one. - fix(deps): point `overrides.sharp` at `$sharp` so the override follows the direct dependency instead of being a second copy of it. Resolves to `^0.35.0` today, so the lockfile is byte-identical and nothing moves. Verified by replaying #206's pin on top: lockfile regenerates and `npm ci` accepts it, where before it was EOVERRIDE then EUSAGE. - chore(config): set `baseBranchPatterns` to the active dev line. All four open dependency PRs target `main`, which the release flow forbids as an independent commit target; sockguard and portwing already pin theirs. - ci(greptile): skip the summon when the PR is already closed. A label can land after close and the frozen reusable workflow fails loudly rather than no-opping ("Pull request #234 is closed"). Staying strict is right for the shared workflow, so the guard belongs in the caller. #208 is a separate cause and is not fixed here: `@vitejs/plugin-react@6` peer-requires `vite@^8` against a pinned `vite@6.4.3`, and no vite major PR exists, so it cannot resolve alone. That wants an ecosystem group in the shared preset.
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 29, 2026 00:45
270e28b to
d8b5277
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
11 times, most recently
from
August 30, 2026 19:12
e3b32cb to
ef1e201
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 30, 2026 20:03
ef1e201 to
dd03752
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
August 30, 2026 20:43
dd03752 to
d29d96d
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
September 2, 2026 15:09
d29d96d to
e05329e
Compare
renovate
Bot
changed the title
This file contains hidden or 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
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:
^4.9.0→4.9.0^0.35.0→0.35.3^0.35.3→0.35.4Add the preset
:preserveSemverRangesto your config if you don't want to pin your dependencies.Configuration
📅 Schedule: (in timezone America/New_York)
🚦 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 was generated by Mend Renovate. View the repository job log.