@dotansimha@ardatan Any chance this can be prioritized?

Thanks@emileriksson ! I added 1 comment about the static schema, otherwise this look good to me.

@emileriksson any idea why CI is failing with latest changes? 👀 I think that's the only blocker we have now

Try trigger it again@dotansimha. The Node jobs go green when I ran this PR on my fork:emileriksson#2

Yeah, this seems great. Thank you@emileriksson.

Can you please add achangeset file? Just runpnpm changeset in the root workspace and it will guide you. We'll need a minor version bump for the affected packages. Once added, we can merge and proceed. Thank you!

Awesome! I added a changeset file with minors to all affected packages@dotansimha 😄

Thanks@emileriksson !

Sorry for the additional requests, but two things came to mind when I discussed this with the team:

• Specifying both--federation and--federationV2 will conflict and yield bad schema. Maybe it can be checked?
• Federation v2 allow the user to use@link directive are rename some of the scalars/directive names. This will fall short for sure with the current implementation. We discussed the need for non-static schema and I think it might be relevant again? 🤔 (I'm ok with addressing this later in a follow up PR, but just wanted to hear your thoughts).

cc@jdolle