chore: remove history future flag #20131
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
remidej
added
source: core:content-manager
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
markkaylor
reviewed
Apr 17, 2024
| @@ -1,7 +1,6 @@ | |||
| export interface FeaturesConfig { | |||
| future?: { | |||
| contentReleases?: boolean; | |||
There was a problem hiding this comment.
@Feranchz I think we should remove this in another PR
markkaylor
approved these changes
Apr 17, 2024
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.
What does it do?
Removes history future flag
Why is it needed?
History is reaching beta status, the same as the rest of v5. And the license check is already live to gatekeep access
How to test it?
History should work without future flags as long as you have a good license