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: setup v5 release channel #36540

Merged
merged 7 commits into from
Sep 7, 2022
Merged

chore: setup v5 release channel #36540

merged 7 commits into from
Sep 7, 2022

Conversation

wardpeet
Copy link
Contributor

@wardpeet wardpeet commented Sep 5, 2022

Description

Setup Gatsby v5 alpha channel. It's similar to our v4 release. We merge everything in master behind _CFLAGS_.MAJOR, this allows us to make breaking changes when publishing v5 but keeping v4 channel working.

We should use _CFLAGS_.MAJOR for all things that's javascript based. For other related files we can use git patches that auto apply in order.

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Sep 5, 2022
@wardpeet wardpeet changed the title chore/v5 setup chore: setup v5 release channel Sep 5, 2022
@wardpeet wardpeet added type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Sep 5, 2022
@wardpeet wardpeet marked this pull request as ready for review September 5, 2022 12:49
@LekoArts
Copy link
Contributor

LekoArts commented Sep 6, 2022

This here also needs an update, right?

COMPILER_OPTIONS = `GATSBY_MAJOR=4`,

@LekoArts
Copy link
Contributor

LekoArts commented Sep 6, 2022

@wardpeet
Copy link
Contributor Author

wardpeet commented Sep 6, 2022

The above we want to keep as is; it's the default that we run with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants