Skip to content

chore(deps): update dependency @next/eslint-plugin-next to v16.1.2#274

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/nextjs-monorepo
Jan 16, 2026
Merged

chore(deps): update dependency @next/eslint-plugin-next to v16.1.2#274
renovate[bot] merged 1 commit intomainfrom
renovate/nextjs-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 18, 2025

This PR contains the following updates:

Package Change Age Confidence
@next/eslint-plugin-next (source) 16.1.116.1.2 age confidence

Release Notes

vercel/next.js (@​next/eslint-plugin-next)

v16.1.2

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 enabled auto-merge (rebase) December 18, 2025 21:42
@renovate renovate bot requested a review from rozsival as a code owner December 18, 2025 21:42
@changeset-bot
Copy link

changeset-bot bot commented Dec 18, 2025

⚠️ No Changeset found

Latest commit: 799e28b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title chore(deps): update dependency @next/eslint-plugin-next to v16.1.0 chore(deps): update dependency @next/eslint-plugin-next to v16.1.0 - autoclosed Dec 18, 2025
@renovate renovate bot closed this Dec 18, 2025
auto-merge was automatically disabled December 18, 2025 21:44

Pull request was closed

@renovate renovate bot deleted the renovate/nextjs-monorepo branch December 18, 2025 21:44
@renovate renovate bot changed the title chore(deps): update dependency @next/eslint-plugin-next to v16.1.0 - autoclosed chore(deps): update dependency @next/eslint-plugin-next to v16.1.1 Dec 22, 2025
@renovate renovate bot reopened this Dec 22, 2025
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch 2 times, most recently from 044e8cb to 9af1475 Compare December 22, 2025 22:44
@renovate renovate bot enabled auto-merge (rebase) December 23, 2025 00:52
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 9af1475 to 719491a Compare December 31, 2025 14:50
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 719491a to 40892d3 Compare January 8, 2026 19:24
@renovate renovate bot changed the title chore(deps): update dependency @next/eslint-plugin-next to v16.1.1 chore(deps): update dependency @next/eslint-plugin-next to v16.1.1 - autoclosed Jan 9, 2026
@renovate renovate bot closed this Jan 9, 2026
auto-merge was automatically disabled January 9, 2026 14:07

Pull request was closed

@renovate renovate bot changed the title chore(deps): update dependency @next/eslint-plugin-next to v16.1.1 - autoclosed chore(deps): update dependency @next/eslint-plugin-next to v16.1.2 Jan 15, 2026
@renovate renovate bot reopened this Jan 15, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch 2 times, most recently from 40892d3 to 799e28b Compare January 15, 2026 00:35
@renovate renovate bot enabled auto-merge (rebase) January 15, 2026 05:31
@renovate renovate bot merged commit 016d049 into main Jan 16, 2026
8 checks passed
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