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(gatsby-plugin-clerk): Backport transition period notice to v4 #3877

Merged
merged 3 commits into from
Aug 1, 2024

Conversation

wobsoriano
Copy link
Member

Description

This PR adds EOL transition notice to Gatsby v4 branch. See original PR here.

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Copy link

changeset-bot bot commented Aug 1, 2024

🦋 Changeset detected

Latest commit: bcde4dc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@wobsoriano wobsoriano changed the title chore(gatsby-plugin-clerk): Add transition period notice chore(gatsby-plugin-clerk): Backport transition period notice to v4 Aug 1, 2024
@wobsoriano wobsoriano marked this pull request as ready for review August 1, 2024 18:33
@wobsoriano wobsoriano requested a review from a team as a code owner August 1, 2024 18:33
@wobsoriano wobsoriano enabled auto-merge (squash) August 1, 2024 18:47
@wobsoriano wobsoriano merged commit e22376a into release/v4 Aug 1, 2024
8 checks passed
@wobsoriano wobsoriano deleted the gatsby-eol-notice-to-v4 branch August 1, 2024 18:52
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.

3 participants