Skip to content

chore(deps): update dependency eslint-config-next to v12.3.7 #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-next (source) 12.3.1 -> 12.3.7 age adoption passing confidence

Release Notes

vercel/next.js (eslint-config-next)

v12.3.7

Compare Source

v12.3.6

Compare Source

v12.3.5

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.
This release contains a security patch for CVE-2025-29927.

Core Changes
  • [backport] middleware subrequest patch (#​77424)

v12.3.4

Compare Source

v12.3.3

Compare Source

v12.3.2

Compare Source


Configuration

📅 Schedule: 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
Copy link

vercel bot commented Mar 17, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
supabase-graphql-example ❌ Failed (Inspect) Mar 29, 2025 7:24pm

@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v12.3.4 chore(deps): update dependency eslint-config-next to v12.3.4 Oct 25, 2023
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v12.3.4 chore(deps): update nextjs monorepo to v12.3.4 Oct 31, 2023
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v12.3.4 chore(deps): update dependency eslint-config-next to v12.3.4 Nov 1, 2023
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v12.3.4 chore(deps): update nextjs monorepo to v12.3.4 Dec 22, 2023
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v12.3.4 chore(deps): update dependency eslint-config-next to v12.3.4 Dec 22, 2023
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v12.3.4 chore(deps): update nextjs monorepo to v12.3.4 Jan 23, 2024
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v12.3.4 chore(deps): update dependency eslint-config-next to v12.3.4 Jan 23, 2024
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v12.3.4 chore(deps): update dependency eslint-config-next to v12.3.5 Mar 23, 2025
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 4ace98a to c228817 Compare March 23, 2025 08:12
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v12.3.5 chore(deps): update dependency eslint-config-next to v12.3.6 Mar 28, 2025
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from c228817 to 699d682 Compare March 28, 2025 04:14
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v12.3.6 chore(deps): update dependency eslint-config-next to v12.3.7 Mar 29, 2025
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 699d682 to 21415eb Compare March 29, 2025 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants