-
Notifications
You must be signed in to change notification settings - Fork 254
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 @apollo/[email protected] #1236
Merged
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
trevor-scheer
force-pushed
the
release-gateway-0.45.0
branch
from
December 8, 2021 01:16
e490145
to
3797c84
Compare
@trevor-scheer I assume you forgot to close this? |
@pcmanus nope this is the next "major" for |
TODO:
|
…`) (#1225) Co-authored-by: Jesse Rosenberger <[email protected]>
trevor-scheer
force-pushed
the
release-gateway-0.45.0
branch
from
December 17, 2021 18:15
44dd614
to
8bd64aa
Compare
This commit adds two new configuration fields to the existing `ManagedGatewayConfig` interface: * `uplinkEndpoints?: string[];` * `uplinkMaxRetries?: number;` If `uplinkEndpoints` is not set and there is an existing setting for `schemaDeliveryMaxRetries` (deprecated) it will be honored. Also, the existing env variable `APOLLO_SCHEMA_CONFIG_DELIVERY_ENDPOINT` is now treated as a comma-separated list of Uplink URLS. `uplinkMaxRetries` will default to three times the number of entries in the end-points array. If you specify more than one Uplink URL, the `loadSupergraphSdlFromUplinks()` logic will round-robin retry and will return the first result it receives. Co-authored-by: David M. Johnson <[email protected]>
- [email protected] - @apollo/[email protected] - @apollo/[email protected] - @apollo/[email protected] - @apollo/[email protected]
- @apollo/[email protected]
- [email protected] - @apollo/[email protected] - @apollo/[email protected] - @apollo/[email protected] - @apollo/[email protected]
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.
As with release PRs in the past, this is a PR tracking a release-gateway-x.y.z branch for an upcoming release. 🙌 The version in the title of this PR should correspond to the appropriate branch.
The intention of these release branches is to gather changes which are intended to land in a specific version (again, indicated by the subject of this PR). Release branches allow additional clarity into what is being staged, provide a forum for comments from the community pertaining to the release's stability, and to facilitate the creation of pre-releases (e.g. alpha, beta, rc) without affecting the version-0.x branch.
PRs for new features might be opened against or re-targeted to this branch by the project maintainers. The main branch may be periodically merged into this branch up until the point in time that this branch is being prepared for release. Depending on the size of the release, this may be once it reaches RC (release candidate) stage with an -rc.x release suffix. Some less substantial releases may be short-lived and may never have pre-release versions.
When this version is officially released onto the latest npm tag, this PR will be merged into version-0.x.