chore(deps): update dependency next-seo to v7 #2794
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.8.0
->7.0.1
Release Notes
garmeeh/next-seo (next-seo)
v7.0.1
Patch Changes
1db3648
: Add JSDoc comment to internal type guard functionv7.0.0
Next SEO v7.0.0 Release Notes
🚨 Important Notice
Next SEO v7 is a complete rewrite with breaking changes throughout the entire API.
We strongly recommend staying on v6 unless you:
Version 6 will continue to receive bug fixes and security updates.
📋 Summary
Next SEO v7 represents a ground-up rewrite of the library, modernizing every aspect from tooling to API design. This release focuses on:
🎯 Why v7?
The web development ecosystem has evolved significantly as well as my skills (I hope) since Next SEO's inception. Version 7 addresses several key challenges:
✨ Major Improvements
1. Modern Build Tooling
2. Enhanced Developer Experience
3. Google-Compliant JSON-LD Components
All JSON-LD components have been rebuilt from scratch following Google's structured data gallery specifications:
4. Simplified Pages Router API
Instead of components that manage Next.js internals, v7 exposes pure functions that you control:
💔 Breaking Changes
Complete API Redesign
This is not a drop-in replacement. Every aspect of the API has changed:
Pages Router Changes
<NextSeo />
generateNextSeo()
function<DefaultSeo />
generateDefaultSeo()
functionnext-seo
next-seo/pages
<Head>
App Router Changes
useAppDir={true}
JSON-LD Component Changes
All components have completely new APIs. Properties have been renamed, restructured, or removed to match Google's specifications.
🔄 Migration Guide
Basic Pages Router Migration
Before (v6):
After (v7):
JSON-LD Migration Example
Before (v6):
After (v7):
🛠️ Technical Improvements
Build System
~
mapping tosrc
Testing Infrastructure
Developer Tooling
📚 Documentation
The documentation has been completely rewritten:
🤝 Contributing
Version 7 makes contributing easier than ever:
🔮 Future Plans
📞 Support
master
branchmain
branchUnless you specifically need the new JSON-LD components or are starting a fresh project, we recommend staying on v6. The API changes are extensive and will require a complete rewrite of your SEO implementation. Version 6 remains stable, battle-tested, and will continue to receive maintenance updates.
Thank you for your continued support of Next SEO. I'm excited about the future of SEO in Next.js applications!
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone UTC, 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.
This PR was generated by Mend Renovate. View the repository job log.