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

release: composition@v2.0.0 #100

Merged
merged 1 commit into from
Apr 11, 2022
Merged

release: composition@v2.0.0 #100

merged 1 commit into from
Apr 11, 2022

Conversation

benweatherman
Copy link
Contributor

No description provided.

Copy link
Contributor

@o0Ignition0o o0Ignition0o left a comment

Choose a reason for hiding this comment

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

Not really sure what is happening here but It might be worth a check (in the error message as well i guess).
Otherwise lgtm! 🙌

@benweatherman
Copy link
Contributor Author

Thanks for double-checking that @o0Ignition0o! That code should be safe to keep around, since it's checking for a minimum version where we support pinning the composition version. It can probably be removed at some point since it would only be helpful for people trying out the 2.x preview releases (which are mostly internal users).

@benweatherman benweatherman merged commit ff44dc4 into main Apr 11, 2022
@benweatherman benweatherman deleted the composition@v2.0.0 branch April 11, 2022 14:51
dingxiangfei2009 pushed a commit to dingxiangfei2009/federation-rs that referenced this pull request Jun 23, 2022
…l#102)

This cargo cults a lot of stuff from the `federation` repository, which has
had this configuration in place for a long time now.

Granted this does add a lot of lines, most of it is to account for our use
of the query-planner written in Node.js within the Router.  The additional
jockery is to account for various learnings and differences between the
operating systems, including how they have to have Node.js installed.

Aside from also running on macOS and Windows, it has various other benefits
that relate to our use cases:

- Hoists the responsibility of toolchain stuff to CircleCI Orbs' Rust pkg
- Pins the version of Node.js (and npm that we depend on for our query
  planner integration, rather than having them be whatever is within the
  CircleCI node variant of the Rust image.

It's certainly possible that we'll want this in the code itself to
facilitate developing on those environments, but I think it's too soon to
invest heavily in having Node.js as a dependency for long-term.

Closes apollographql#91
Closes apollographql#100

Co-authored-by: Jesse Rosenberger <git@jro.cc>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants