Skip to content
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

chore(deps): Update devDependency @nuxt/eslint to v1 #682

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/eslint (source) ^0.7.6 -> ^1.0.0 age adoption passing confidence

Release Notes

nuxt/eslint (@​nuxt/eslint)

v1.0.0

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 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 force-pushed the renovate/nuxt-eslint-1.x branch from 038e152 to 8660bbe Compare January 31, 2025 14:13
@daniluk4000 daniluk4000 enabled auto-merge January 31, 2025 14:27
@renovate renovate bot force-pushed the renovate/nuxt-eslint-1.x branch from 8660bbe to 545ed2a Compare January 31, 2025 14:44
@renovate renovate bot force-pushed the renovate/nuxt-eslint-1.x branch from 545ed2a to 22ae68a Compare January 31, 2025 14:46
@daniluk4000 daniluk4000 merged commit d485e62 into next Jan 31, 2025
3 checks passed
@daniluk4000 daniluk4000 deleted the renovate/nuxt-eslint-1.x branch January 31, 2025 14:48
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.

1 participant