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: v0.24.0 #1973

Merged
merged 1 commit into from
Jul 15, 2024
Merged

release: v0.24.0 #1973

merged 1 commit into from
Jul 15, 2024

Conversation

jonathanrainer
Copy link
Contributor

@jonathanrainer jonathanrainer commented Jul 12, 2024

[0.24.0]

Important: 1 potentially breaking change below, indicated by ❗ BREAKING ❗

❗ BREAKING ❗

  • Removed the deprecated plain and json options for --output - @dylan-apollo PR #1804

    The --output option is now only for specifying a file to write to. The --format option should be used to specify the format of the output.

🚀 Features

  • Return the name of the linting rule that is violated, as well as the code - @jonathanrainer PR #1907

    Originally only the message from the linting violation was included in the response, but now it also includes the name of the specific linting rule to aid debugging

  • Use the Router's /health?ready endpoint to check readiness - @nmoutschen PR #1939

    Previously rover dev used a simple query to establish readiness, but this did not allow for router customizations.

  • Adding architecture and OS metrics - @aaronArinder PR #1947

    Allows us to track the Operating Systems and Architectures in use by our users, this will give us more information as to where to focus support efforts

  • Allow aarch64 macOS to pull correct supergraph binaries where available - @jonathanrainer PR #1971

    We recently started publishing supergraph binaries for aarch64, so if they are available Rover will use them in preference to x86_64 binaries.

🐛 Fixes

  • Don't panic if the telemetry client cannot be initialised - @dylan-apollo PR #1897 - Issue #1893

  • Rename .cargo/config to .cargo/config.toml - @jonathanrainer PR #1921

  • Fix pnpm installs by moving the binary download location - @jonathanrainer PR #1927 - Issue #1881

    After we inlined the binary-install dependency in v0.23.0 this changed where the downloaded binary was stored when using pnpm. This caused users running the binary to enter an infinite loop. This moves the binary to a new location which avoids this.

  • Don't panic on file watcher errors - @nmoutschen PR #1935

    Instead of panicking when errors occur watching files return those errors gracefully to the user.

  • Store binaries with version numbers attached so upgrades are possible - @jonathanrainer PR #1932 - Issue #1563

    When downloading binaries via npm they were always stored as rover despite the version. As such, when a new version came out the upgrade would fail. This now doesn't happen, as binaries are stored with their versions number in the name.

  • Ensure correct URL is used if subgraph_url and routing_url are provided in a supergraph schema - @jonathanrainer PR #1948 - Issue #1782

  • Let --output accept paths with missing intermediate directories - @jonathanrainer PR #1944 - Issue #1787

  • Allow rover dev to read Federation Version from supergraph schema - @jonathanrainer PR #1950 - Issue #1735

    The Federation version could be set in the supegraph schema but was being ignored by rover dev. It now is taken into account, along with the overriding environment variable.

  • Stop .exe being printed after Federation version during composition - @jonathanrainer PR #1951 - Issue #1390

  • Reinstate support for glibc 2.17 - @jonathanrainer PR #1953

    In resolving the issues with CentOS 7 we accidentally removed support for glibc 2.17, this has now been restored

  • Be more lenient about supergraph binary versions - @dylan-apollo PR #1966

    In resolving rover supergraph compose erroneously includes .exe in message suffix on windows #1390, we were too restrictive in what counted as a valid version. This restores the correct behaviour

  • Set package.json to a stable version when testing NPM Installers - @jonathanrainer PR #1967

    When testing whether our NPM installers worked correctly we were trying to download the latest rover binary. On release PRs, where the binary didn't yet exist, this was causing problems.

  • Fix mocking of calls to Orbiter in Installer tests - @jonathanrainer PR #1968

  • Remove noisy errors from intermediate composition states - @aaronArinder PR #1956

    When rover dev composes multiple subgraphs it does so one at a time. As such if there are dependencies there can be noisy ephemeral errors, this fixes that by waiting until all subgraphs are added before trying composition.

🛠 Maintenance

📚 Documentation

  • Minor update to README.md - @tratzlaff PR #1880

    Fixes use of numbered lists in the README.md

  • Remove failing/redundant links from docs - @dotdat PR #1894

  • Update docs style - @Meschreiber PR #1883

    Update formatting and admonitions to most recent conventions.

  • Update frontmatter - @Meschreiber PR #1898

    Updates title casing and adds metadata to subtitles

  • Clarify subgraph publish can only create variants not graphs - @Meschreiber PR #1938

  • Make example using - instead of filepath clearer - @aaronArinder PR #1963

  • Update Router terminology - @Meschreiber PR #1925

    Update the uses of Apollo Router to GraphOS Router or Apollo Router Core where necessary

  • Update documentation to make it clear we collect CPU Architecture, per command - @aaronArinder PR #1964

@jonathanrainer jonathanrainer merged commit 96cbc49 into main Jul 15, 2024
19 checks passed
@jonathanrainer jonathanrainer deleted the 0.24.0 branch July 15, 2024 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚢 release release PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants