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

fix: Restore compatibility with next@latest #395

Merged
merged 1 commit into from
Nov 16, 2023
Merged

Conversation

franky47
Copy link
Member

@franky47 franky47 commented Nov 14, 2023

This is to be released when [email protected] lands.

  • Update semver compatibility range to >=13.4 <14.0.2 || ^14.0.3
  • Test latest against WHS true/false rather than canary (already tested on the canary-specific CI)
  • Update docs (version compatibility table)
  • Update CI to replace 14.0.1 with latest (and update branch protection to match) Keep 14.0.1 in tests.

Copy link

vercel bot commented Nov 14, 2023

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

Name Status Preview Comments Updated (UTC)
next-usequerystate ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 16, 2023 7:14pm

@franky47 franky47 marked this pull request as ready for review November 16, 2023 21:28
@franky47 franky47 merged commit d9eb84a into next Nov 16, 2023
12 checks passed
@franky47 franky47 deleted the fix/12.0.3-compat branch November 16, 2023 21:32
Copy link

🎉 This PR is included in version 1.12.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant