-
Notifications
You must be signed in to change notification settings - Fork 94
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
adds docs on using the native GitHub actions #2419
Conversation
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 1 changed, 0 removed
Build ID: b52e04e16e419eb707960712 URL: https://www.apollographql.com/docs/deploy-preview/b52e04e16e419eb707960712 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this addition! Beyond the nits I've added as suggestions/comments, a couple of wonderings:
- Should we also update https://www.apollographql.com/docs/graphos/platform/schema-management/checks/github-integration?
- I'm wondering if the H3 orders in the H2 GitHub Actions best fits users' needs. for example, should the new
Apollo-provided GitHub Actions
go first, followed by[Linux/MacOS jobs using the curl installer](https://www.apollographql.com/docs/deploy-preview/8fc8083fd1146f0f092571d9/rover/ci-cd#linuxmacos-jobs-using-the-curl-installer)
then[Displaying schema check results on GitHub pull requests](https://www.apollographql.com/docs/deploy-preview/8fc8083fd1146f0f092571d9/rover/ci-cd#displaying-schema-check-results-on-github-pull-requests)
? Or are the following two sub-headers of[Displaying schema check results on GitHub pull requests](https://www.apollographql.com/docs/deploy-preview/8fc8083fd1146f0f092571d9/rover/ci-cd#displaying-schema-check-results-on-github-pull-requests)
?
Co-authored-by: Maria Elisabeth Schreiber <[email protected]>
re:
I think moving them to the same heading level (H3) makes the most sense, since they're all related but not nested. The GitHub app is helpful for both options, but does require a slight bit of configuration in addition to the others. It could live below them- what do you think? |
# [0.28.0] - 2025-03-12 ## 🚀 Features - **Default to Apollo Router 2.x for `rover dev` - @pubmodmatt PR #2433** The default version of Apollo Router used by `rover dev` is now 2.x instead of 1.x. The default can be overridden by setting `APOLLO_ROVER_DEV_ROUTER_VERSION`, for example `APOLLO_ROVER_DEV_ROUTER_VERSION=1.61.0`. - **Implement supergraph config schema command - @jonathanrainer PR #2418** Adds a new `rover supergraph config schema` command to output the JSONSchema for `supergraph.yaml`. This can be used to configure editor support for the file. ## 🐛 Fixes - **Add specific CompositionError handling - @jonathanrainer PR #2422** - **Pass log_level through to Router binary - @monkpow PR #2426** - **Fix formatting of table output by `rover config whoami` - @pubmodmatt PR #2413** - **Better error on missing environment variable - @pubmodmatt PR #2442** ## 🛠 Maintenance - **Add Apollo Router 2.x dependency to renovate - @pubmodmatt PR #2430** - **Fix CI post update to Rustup 1.28 - @jonathanrainer PR #2431** - **Replace backoff with backon - @pubmodmatt PR #2437** - **Add exemption for unmaintained humantime dependency - @pubmodmatt PR #2440** ## 📚 Documentation - **Add docs on using the native GitHub actions - @lleadbet PR #2419** - **Add changelog entry for new behaviour w.r.t subgraph_url - @jonathanrainer PR #2420** - **GitHub CI/CD - @shorgi PR #2427**
As we've moved the GitHub Actions into a more formally supported repo (https://github.com/apollographql/rover-actions), this just updates the docs to point folks there vs. just the cURL example.