Skip to content

chore(deps): update dependency eslint-plugin-astro to ~2.1.0#1286

Open
renovate[bot] wants to merge 1 commit into
promplate-demofrom
renovate/eslint-plugin-astro-2.x
Open

chore(deps): update dependency eslint-plugin-astro to ~2.1.0#1286
renovate[bot] wants to merge 1 commit into
promplate-demofrom
renovate/eslint-plugin-astro-2.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
eslint-plugin-astro (source) ~2.0.0 → ~2.1.0 age confidence

Release Notes

ota-meshi/eslint-plugin-astro (eslint-plugin-astro)

v2.1.1

Compare Source

Patch Changes
  • #​588 3a04d1e Thanks @​ota-meshi! - Fix false positives in astro/no-omitted-end-tags for component names that overlap with HTML tag names, such as <Head>, while preserving reported source offsets.

v2.1.0

Compare Source

Minor Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

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

@vercel

vercel Bot commented Jun 27, 2026 •
edited
Loading

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
endless-chat Error Error Jul 25, 2026 1:26am
free-chat Error Error Jul 25, 2026 1:26am

@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from e27d563 to 4a29c74 Compare July 1, 2026 00:29
@CNSeniorious000
CNSeniorious000 force-pushed the promplate-demo branch 2 times, most recently from cbfcefa to 3304a26 Compare July 11, 2026 22:55
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from 4a29c74 to 98631e7 Compare July 12, 2026 12:28
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from 98631e7 to c61656b Compare July 15, 2026 01:12
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from c61656b to 397432e Compare July 16, 2026 23:56
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from 397432e to d40f268 Compare July 17, 2026 01:25
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from d40f268 to 80101fe Compare July 20, 2026 16:10
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from 80101fe to f2132e4 Compare July 21, 2026 01:23
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from f2132e4 to 9a8d279 Compare July 24, 2026 16:09
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-astro-2.x branch from 9a8d279 to f3927fc Compare July 25, 2026 01:26
@renovate

renovate Bot commented Jul 25, 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 (1522 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 57, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (1522 entries in 4.2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  svelte@5.56.8 was published at 2026-07-24T22:09:08.000Z, within the minimumReleaseAge cutoff (2026-07-24T01:26:05.396Z)

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.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants