Skip to content

Conversation

@theguild-bot
Copy link
Collaborator

@theguild-bot theguild-bot commented Dec 3, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

hive@8.13.0

Minor Changes

  • #7303
    840bc08
    Thanks @adambenhassen! - Add configurable data retention TTL
    for self-hosted Hive instances. Self-hosted users can now configure retention periods via
    environment variables instead of hardcoded values.

    New environment variables:

    • CLICKHOUSE_TTL_TABLES - Retention for ClickHouse mergetree tables (Default: 1 YEAR)
    • CLICKHOUSE_TTL_DAILY_MV_TABLES - Retention for daily materialized view tables (Default: 1
      YEAR)
    • CLICKHOUSE_TTL_HOURLY_MV_TABLES - Retention for hourly materialized view tables (Default: 30
      DAYS)
    • CLICKHOUSE_TTL_MINUTELY_MV_TABLES - Retention for minutely materialized view tables (Default:
      24 HOURS)

    Supports both numeric days (e.g., 365) and ClickHouse interval syntax (e.g., "1 YEAR",
    "30 DAY", "24 HOUR").

    The retention update runs automatically if any retention environment variable is set.

  • #7333
    4aa5247
    Thanks @alexdaima! - Update Redis client to support connecting to
    IPv6 networks.

  • #7400
    c396566
    Thanks @n1ru4l! - Add support for retrieving CDN artifacts by version
    ID.

    New CDN endpoints allow fetching schema artifacts for a specific version:

    • /artifacts/v1/:targetId/version/:versionId/:artifactType
    • /artifacts/v1/:targetId/version/:versionId/contracts/:contractName/:artifactType

    Artifacts are now written to both the latest path and a versioned path during schema publish,
    enabling retrieval of historical versions.

    CDN artifact responses now include the x-hive-schema-version-id header, providing the version ID
    of the schema being served.

Patch Changes

  • #7381
    415a9c1
    Thanks @jdolle! - Hide unnecessary elements from header when screen
    is narrow

  • #7352
    727e525
    Thanks @jdolle! - Correctly check the global environment feature flag
    in for app deployments and fix app deployment pagination

  • #7402
    4183e55
    Thanks @n1ru4l! - Improve native federation schema composition.
    Prevent subgraph-specific federation types and scalars being re-declared within the subgraph
    leaking into the supergraph.

  • #7391
    d027f99
    Thanks @n1ru4l! - Fix exception raised by server when updating user
    profile information.

  • #7389
    a9a3e5f
    Thanks @n1ru4l! - Do not swallow 4XX HTTP errors as 500 internal
    server errors when sentry error reporting is enabled.

    Send the same predictable error responses with and without the sentry plugin enabled.

hive-apollo-router-plugin@2.3.5

Patch Changes

hive-console-sdk-rs@0.2.2

Patch Changes

  • #7405
    24c0998
    Thanks @ardatan! - Use the JSON Schema specification of the usage
    reports directly to generate Rust structs as a source of truth instead of manually written types

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @theguild-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated release PR generated by the Changesets GitHub action. Its purpose is to prepare the hive, hive-apollo-router-plugin, and hive-console-sdk-rs packages for their upcoming respective releases, incorporating recent bug fixes and dependency updates. Merging this PR will trigger the automatic publication of these updated packages to npm.

Highlights

  • hive package update: The hive package has been updated to version 8.12.1, including a fix for an invalid materialized view definition that caused ClickHouse migration failures and a stricter CORS assessment for requests with an Origin header.
  • hive-apollo-router-plugin update: The hive-apollo-router-plugin has been updated to version 2.3.4, primarily to reflect an updated dependency on hive-console-sdk-rs.
  • hive-console-sdk-rs update: The hive-console-sdk-rs package has been updated to version 0.2.1, addressing a bug where reports were not being sent correctly due to missing headers.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🚀 Snapshot Release (rc)

The latest changes of this PR are available as rc on npm (based on the declared changesets):

Package Version Info
hive 8.13.0-rc-20251211143917-eb1f4bcb5ea4f36bc6d79733498a3799660ce406 npm ↗︎ unpkg ↗︎
hive-apollo-router-plugin 2.3.5-rc-20251211143917-eb1f4bcb5ea4f36bc6d79733498a3799660ce406 npm ↗︎ unpkg ↗︎
hive-console-sdk-rs 0.2.2-rc-20251211143917-eb1f4bcb5ea4f36bc6d79733498a3799660ce406 npm ↗︎ unpkg ↗︎

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

📚 Storybook Deployment

The latest changes are available as preview in: https://pr-7367.hive-storybook.pages.dev

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates version numbers across deployment, hive-apollo-router-plugin, and hive-console-sdk-rs packages, along with their respective CHANGELOG.md files. These changes are consistent with an automated release process.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

💻 Website Preview

The latest changes are available as preview in: https://pr-7367.hive-landing-page.pages.dev

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🐋 This PR was built and pushed to the following Docker images:

Targets: build

Platforms: linux/amd64

Image Tag: eb1f4bcb5ea4f36bc6d79733498a3799660ce406

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🐋 This PR was built and pushed to the following Docker images:

Targets: apollo-router-hive-build

Platforms: linux/amd64

Image Tag: 39626fb53ca62b86ae9e634dc7003aad2c580abc

@theguild-bot theguild-bot force-pushed the changeset-release/main branch from 9693a05 to 9f28203 Compare December 4, 2025 00:08
@theguild-bot theguild-bot force-pushed the changeset-release/main branch 2 times, most recently from 8ef3366 to 601796d Compare December 4, 2025 10:02
@theguild-bot theguild-bot force-pushed the changeset-release/main branch 2 times, most recently from 692bb91 to b73f199 Compare December 4, 2025 10:12
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from b73f199 to 4bc3ac3 Compare December 4, 2025 10:18
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from 4bc3ac3 to d6d9231 Compare December 4, 2025 12:13
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from d6d9231 to e6eab8b Compare December 4, 2025 12:17
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from e6eab8b to 3c26229 Compare December 5, 2025 12:43
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from d0ebd51 to 6c6442a Compare December 9, 2025 21:52
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from 6c6442a to b8c6872 Compare December 10, 2025 00:11
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from b8c6872 to 955af12 Compare December 10, 2025 08:39
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from 955af12 to bc2016a Compare December 10, 2025 10:31
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from bc2016a to 0d03bfa Compare December 10, 2025 13:08
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from 0d03bfa to e281477 Compare December 10, 2025 13:26
@theguild-bot theguild-bot force-pushed the changeset-release/main branch from e281477 to 3fe8f24 Compare December 11, 2025 11:58
@n1ru4l n1ru4l merged commit 1cf5606 into main Dec 11, 2025
67 of 71 checks passed
@n1ru4l n1ru4l deleted the changeset-release/main branch December 11, 2025 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants