Skip to content

chore(deps): update dependency daisyui to v5.6.3#196

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/daisyui-5.x
Open

chore(deps): update dependency daisyui to v5.6.3#196
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/daisyui-5.x

Conversation

@renovate

@renovate renovate Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
daisyui (source) 5.5.235.6.3 age confidence

Release Notes

saadeghi/daisyui (daisyui)

v5.6.3

Compare Source

Bug Fixes

v5.6.2

Compare Source

Bug Fixes
  • Missing outline and separators for joined buttons. closes: #​4586 (3f94950)

v5.6.1

Compare Source

Bug Fixes

v5.6.0

Compare Source

Features

Configuration

📅 Schedule: (in timezone Asia/Bangkok)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
? Verifying lockfile against supply-chain policies (650 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 45, reused 0, downloaded 0, added 0
Progress: resolved 49, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (650 entries in 6s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  prettier@3.8.5 was published at 2026-06-26T12:58:13.266Z, within the minimumReleaseAge cutoff (2026-06-26T01:43:24.910Z)

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.

@vercel

vercel Bot commented Jun 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
coding-stats Error Error Jun 27, 2026 1:43am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant