chore(deps): bump lucide-react from 1.17.0 to 1.18.0 in /admin in the prod-minor-patch group#283
Conversation
Bumps the prod-minor-patch group in /admin with 1 update: [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react). Updates `lucide-react` from 1.17.0 to 1.18.0 - [Release notes](https://github.com/lucide-icons/lucide/releases) - [Commits](https://github.com/lucide-icons/lucide/commits/1.18.0/packages/lucide-react) --- updated-dependencies: - dependency-name: lucide-react dependency-version: 1.18.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: prod-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Dependabot bumped lucide-react in admin/package.json to ^1.18.0 but did not regenerate the workspace root pnpm-lock.yaml, so CI failed with ERR_PNPM_OUTDATED_LOCKFILE under --frozen-lockfile. Regenerate the lockfile entry (lockfile-only) to match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
CI installs the latest pnpm, which enforces a default 24h minimumReleaseAge supply-chain gate on the lockfile. Dependabot opens npm bumps the same day a version is published, so the resulting PRs fail CI with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION (e.g. lucide-react 1.18.0 in #283). Add a 3-day cooldown to the /ui and /admin npm update configs so Dependabot waits until a release has aged past the gate before opening a PR. This keeps the supply-chain protection intact while avoiding PRs that are doomed to fail. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
|
Looks like lucide-react is no longer updatable, so this is no longer needed. |
Pull request was closed
Bumps the prod-minor-patch group in /admin with 1 update: lucide-react.
Updates
lucide-reactfrom 1.17.0 to 1.18.0Release notes
Sourced from lucide-react's releases.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions