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 dependency @nuxt/content to v3 (doc-driven) #1054

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/content (source) ^2.13.4 -> ^3.0.1 age adoption passing confidence

Release Notes

nuxt/content (@​nuxt/content)

v3.0.1

Compare Source

Bug Fixes

v3.0.0

Compare Source

Bug Fixes

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.

@renovate renovate bot force-pushed the renovate/doc-driven-nuxt-content-3.x branch from 0623d86 to 8ff982e Compare January 25, 2025 13:59
@renovate renovate bot force-pushed the renovate/doc-driven-nuxt-content-3.x branch from 8ff982e to c368efb Compare January 27, 2025 15:40
@danielroe danielroe closed this Jan 29, 2025
@danielroe danielroe deleted the renovate/doc-driven-nuxt-content-3.x branch January 29, 2025 16:43
Copy link
Author

renovate bot commented Jan 29, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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