Skip to content

chore(deps): bump lucide-react from 1.17.0 to 1.18.0 in /admin in the prod-minor-patch group#283

Closed
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/admin/prod-minor-patch-667bac691f
Closed

chore(deps): bump lucide-react from 1.17.0 to 1.18.0 in /admin in the prod-minor-patch group#283
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/admin/prod-minor-patch-667bac691f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 12, 2026

Copy link
Copy Markdown
Contributor

Bumps the prod-minor-patch group in /admin with 1 update: lucide-react.

Updates lucide-react from 1.17.0 to 1.18.0

Release notes

Sourced from lucide-react's releases.

Version 1.18.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.17.0...1.18.0

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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

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 dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 12, 2026
@github-actions github-actions Bot enabled auto-merge (squash) June 12, 2026 16:14
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>
@qodo-free-for-open-source-projects

Copy link
Copy Markdown

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: test (ubuntu-latest, amd64)

Failed stage: Install pnpm dependencies [❌]

Failed test name: ""

Failure summary:

The action failed during dependency installation because pnpm install --frozen-lockfile rejected
pnpm-lock.yaml due to a supply-chain policy violation.
- pnpm reported
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION]: the lockfile includes lucide-react@1.18.0, which was
published too recently (within the configured minimumReleaseAge cutoff), so the lockfile
verification failed.
- As a result, pnpm install exited with code 1, causing the GitHub Action to
fail.

Relevant error logs:
1:  ##[group]Runner Image Provisioner
2:  Hosted Compute Agent
...

250:  Removing HTTP extra header
251:  [command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
252:  [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
253:  Removing includeIf entries pointing to credentials config files
254:  [command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
255:  [command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
256:  [command]/usr/bin/git config --file /home/runner/work/_temp/git-credentials-a0b6f20d-6a1d-4e14-a25c-a962628d59d6.config http.https://github.com/.extraheader AUTHORIZATION: basic ***
257:  [command]/usr/bin/git config --local includeIf.gitdir:/home/runner/work/etherpad-go/etherpad-go/.git.path /home/runner/work/_temp/git-credentials-a0b6f20d-6a1d-4e14-a25c-a962628d59d6.config
258:  [command]/usr/bin/git config --local includeIf.gitdir:/home/runner/work/etherpad-go/etherpad-go/.git/worktrees/*.path /home/runner/work/_temp/git-credentials-a0b6f20d-6a1d-4e14-a25c-a962628d59d6.config
259:  [command]/usr/bin/git config --local includeIf.gitdir:/github/workspace/.git.path /github/runner_temp/git-credentials-a0b6f20d-6a1d-4e14-a25c-a962628d59d6.config
260:  [command]/usr/bin/git config --local includeIf.gitdir:/github/workspace/.git/worktrees/*.path /github/runner_temp/git-credentials-a0b6f20d-6a1d-4e14-a25c-a962628d59d6.config
261:  ##[endgroup]
262:  ##[group]Fetching the repository
263:  [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/* +f495afe0cbccf456528ffa9ff088a497ef1a941d:refs/remotes/pull/283/merge
264:  From https://github.com/ether/etherpad-go
265:  * [new branch]      125-error-reading-plugin-file            -> origin/125-error-reading-plugin-file
266:  * [new branch]      dependabot/npm_and_yarn/admin/prod-minor-patch-667bac691f -> origin/dependabot/npm_and_yarn/admin/prod-minor-patch-667bac691f
...

447:  REGISTRY_IMAGE: ghcr.io/ether/etherpad-go
448:  GOTOOLCHAIN: local
449:  ##[endgroup]
450:  added 1 package in 2s
451:  1 package is looking for funding
452:  run `npm fund` for details
453:  ##[group]Run pnpm install --frozen-lockfile
454:  �[36;1mpnpm install --frozen-lockfile�[0m
455:  shell: /usr/bin/bash -e {0}
456:  env:
457:  REGISTRY_IMAGE: ghcr.io/ether/etherpad-go
458:  GOTOOLCHAIN: local
459:  ##[endgroup]
460:  Scope: all 17 workspace projects
461:  ? Verifying lockfile against supply-chain policies (173 entries)...
462:  ✗ Lockfile failed supply-chain policy check (173 entries in 1.5s)
463:  [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
464:  lucide-react@1.18.0 was published at 2026-06-12T12:40:55.000Z, within the minimumReleaseAge cutoff (2026-06-11T20:05:25.745Z)
465:  The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
466:  ##[error]Process completed with exit code 1.
467:  Post job cleanup.

SamTV12345 added a commit that referenced this pull request Jun 12, 2026
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>
@dependabot @github

dependabot Bot commented on behalf of github Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

Looks like lucide-react is no longer updatable, so this is no longer needed.

@dependabot dependabot Bot closed this Jun 12, 2026
auto-merge was automatically disabled June 12, 2026 20:32

Pull request was closed

@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/admin/prod-minor-patch-667bac691f branch June 12, 2026 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant