BREAKING: drop Federation v1 support #1978
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
Federation v2 was released almost 3 years ago. It is an evolution of the Federation spec to make it more powerful, flexible and easier to adopt. It is no longer possible to create Federated Supergraphs targeting v1 composition. Users still using fed v1 shoul migrate ASAP to the fed v2.
dariuszkuc
added
changes: major
Apollo Federation Subgraph Compatibility Results
Learn more: |
samuelAndalon
approved these changes
Jun 26, 2024
Merged
1 task
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.
📝 Description
Federation v2 was released almost 3 years ago. It is an evolution of the Federation spec to make it more powerful, flexible and easier to adopt.
It is no longer possible to create Federated Supergraphs targeting v1 composition. Users still using fed v1 shoul migrate ASAP to the fed v2.
🔗 Related Issues