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(packages): make unstable_shouldOnCreateNode stable #36516

Merged
merged 6 commits into from Oct 20, 2022

Conversation

marvinjude
Copy link
Contributor

@marvinjude marvinjude commented Sep 1, 2022

Description

Make unstable_shouldOnCreateNode stable

Documentation

https://www.gatsbyjs.com/docs/reference/config-files/gatsby-node/#unstable_shouldOnCreateNode

[sc-53835]

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Sep 1, 2022
@marvinjude marvinjude closed this Sep 1, 2022
@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Oct 4, 2022
@LekoArts LekoArts reopened this Oct 19, 2022
@LekoArts LekoArts added this to the Gatsby 5 milestone Oct 19, 2022
@LekoArts LekoArts added the topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine) label Oct 19, 2022
Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢 🇮🇹

@LekoArts LekoArts merged commit 90f9ab4 into master Oct 20, 2022
@LekoArts LekoArts deleted the make-unstable-create-node-stable branch October 20, 2022 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants