Dismissing the Warning on Gatsby 3+ #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
based on the discussion on ifiokjr#40 and these instructions for plugin maintainers. https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/#for-plugin-maintainers The plugin itself works for me for a while now on the latest 3 gatsby without issue.
|
Thanks for creating the PR. I'll merge it once it builds. |
|
Cool!
Noting that I was not able to setup my environment (unrelated to this
change) so it was not built and tested yet.
…On Sat, Aug 28, 2021 at 7:00 PM Ifiok Jr. ***@***.***> wrote:
Thanks for creating the PR. I'll merge it once it builds.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#58 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCPKMZBDLTZFYD2XDJHBO3T7EB2PANCNFSM5C6CZQXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
github-actions bot
pushed a commit
that referenced
this pull request
Aug 30, 2021
## [1.8.0](v1.7.0...v1.8.0) (2021-08-30) ### Features * add support for `gatsby@3` ([#58](#58)) ([173d5df](173d5df))
|
🎉 This PR is included in version 1.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
santa512
added a commit
to santa512/gatsby-plugin-next-seo
that referenced
this pull request
Mar 4, 2024
## [1.8.0](ifiokjr/gatsby-plugin-next-seo@v1.7.0...v1.8.0) (2021-08-30) ### Features * add support for `gatsby@3` ([#58](ifiokjr/gatsby-plugin-next-seo#58)) ([173d5df](ifiokjr/gatsby-plugin-next-seo@173d5df))
stacksculptor
added a commit
to stacksculptor/Resilio
that referenced
this pull request
May 23, 2024
## [1.8.0](ifiokjr/gatsby-plugin-next-seo@v1.7.0...v1.8.0) (2021-08-30) ### Features * add support for `gatsby@3` ([#58](ifiokjr/gatsby-plugin-next-seo#58)) ([173d5df](ifiokjr/gatsby-plugin-next-seo@173d5df))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
based on the discussion on
#40
and these instructions for plugin maintainers.
https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/#for-plugin-maintainers
The plugin itself works for me for a while now on the latest 3 gatsby without issue.
Closes #40
Description
Checklist
yarn fixruns successfully.yarn api:generateand updated the README documentation where necessary.yarn test && yarn test:e2e.