Upcoming Release Changes

[theguild-bot]

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@9.5.0

Minor Changes

• #7699
  5f88ce8
  Thanks @n1ru4l! - Add experimental support for running without
  supertokens service.

  Instructions

  Prerequisites

  Adjust your docker compose file like the following:

  • Remove services.supertokens from your docker-compose.community.yml file
  • Remove the following environment variables from the services.server.environment
    • SUPERTOKENS_CONNECTION_URI=
    • SUPERTOKENS_API_KEY=
  • Set the following environment variables for services.server.environment
    • SUPERTOKENS_AT_HOME=1
    • SUPERTOKENS_REFRESH_TOKEN_KEY=
    • SUPERTOKENS_ACCESS_TOKEN_KEY=
  • Set the following environment variables for services.migrations.environment
    • SUPERTOKENS_AT_HOME=1

  Set the refresh token key

  Extract from existing supertokens deployment

  This method works if you use supertokens before and want to have existing user sessions to
  continue working. If you want to avoid messing with the database, you can also create a new
  refresh token key from scratch, the drawback is that users are forced to login again.

  Extract the refresh token key from the supertokens database

  SELECT
    "value"
  FROM
    "supertokens_key_value"
  WHERE
    "name" = 'refresh_token_key';

  The key should look similar to this:
  1000:15e5968d52a9a48921c1c63d88145441a8099b4a44248809a5e1e733411b3eeb80d87a6e10d3390468c222f6a91fef3427f8afc8b91ea1820ab10c7dfd54a268:39f72164821e08edd6ace99f3bd4e387f45fa4221fe3cd80ecfee614850bc5d647ac2fddc14462a00647fff78c22e8d01bc306a91294f5b889a90ba891bf0aa0

  Update the docker compose services.server.environment.SUPERTOKENS_REFRESH_TOKEN_KEY environment
  variable value to this string.

  Create from scratch

  Run the following command to create a new refresh key from scratch:

  echo "1000:$(openssl rand -hex 64):$(openssl rand -hex 64)"

  Update the docker compose services.server.environment.SUPERTOKENS_REFRESH_TOKEN_KEY environment
  variable value to this string.

  Set the access token key

  Generate a new access token key using the following instructions:

  # 1. Generate a unique key name. 'uuidgen' is great for this.
  #    You can replace this with any string you like, e.g., KEY_NAME="my-app-key-1"
  KEY_NAME=$(uuidgen)
  # 2. Generate a 2048-bit RSA private key in PEM format, held in memory.
  PRIVATE_KEY_PEM=$(openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048)
  # 3. Extract the corresponding public key from the private key, also held in memory.
  PUBLIC_KEY_PEM=$(echo "$PRIVATE_KEY_PEM" | openssl rsa -pubout)
  # 4. Strip the headers/footers and newlines from the private key PEM
  #    to get just the raw Base64 data.
  PRIVATE_KEY_DATA=$(echo "$PRIVATE_KEY_PEM" | awk 'NF {if (NR!=1 && $0!~/-----END/) print}' | tr -d '\n')
  # 5. Do the same for the public key PEM.
  PUBLIC_KEY_DATA=$(echo "$PUBLIC_KEY_PEM" | awk 'NF {if (NR!=1 && $0!~/-----END/) print}' | tr -d '\n')
  # 6. Echo the final formatted string to the console.
  echo "${KEY_NAME}|${PUBLIC_KEY_DATA}|${PRIVATE_KEY_DATA}"

  Update the docker compose services.server.environment.SUPERTOKENS_ACCESS_TOKEN_KEY environment
  variable value to the formatted string output.

  Conclusion

  After performing this updates you can run Hive Console without the need for the supertokens
  service. All the relevant authentication logic resides within the server container instead.

  Existing users in the supertokens system will continue to exist when running without the
  supertokens service.

Patch Changes

• #7732
  3567483
  Thanks @jonathanawesome! - fix: correct RPM chart Y-axis
  scale to match actual values

[gemini-code-assist]

Summary of Changes

Hello @theguild-bot, I'm Gemini Code Assist¹! 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, automatically generated by the Changesets release action, prepares for the hive@9.5.0 release. The primary feature introduced is an experimental capability to run the Hive Console without requiring a dedicated supertokens service, streamlining deployment by consolidating authentication logic within the main server. This release also includes updates to documentation and version numbers to reflect the new release.

Highlights

• Experimental Supertokens-less Operation: Added experimental support for running the Hive Console without the need for a separate supertokens service, consolidating authentication logic within the main server container.

Changelog

• deployment/CHANGELOG.md
  • Added the changelog entry for hive@9.5.0, detailing the new experimental support for running without a supertokens service, including comprehensive instructions for configuration.

Activity

• This pull request was automatically opened by the Changesets release GitHub action.
• No human activity has occurred on this pull request yet.

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]

🚀 Snapshot Release (rc)

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

Package	Version	Info
hive	9.5.0-rc-20260225150148-47668f34b4eebcd868637b7ed239a809a1bb7cc8	npm ↗︎ unpkg ↗︎

[gemini-code-assist]

Code Review

This PR updates the Hive Console deployment to version 9.5.0, including changes to the docker-compose file download links, docker tag, and related documentation. It also removes a now-obsolete changeset file and adds a Cargo.lock file to .gitignore. The most significant change is the addition of experimental support for running without the supertokens service, requiring updates to environment variables and docker-compose configurations. I have added a comment to address a potential issue with the wget/curl links in the documentation.

[gemini-code-assist]

The wget and curl commands are downloading the docker-compose file directly from the hive branch. If the intention is to download a stable version, it would be better to use the main branch or a specific tag to avoid unexpected changes. Using the main branch ensures users always get the latest stable version, while using a specific tag ensures reproducibility.

Consider updating the URL to point to main or a specific release tag.

[github-actions]

💻 Website Preview

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

[github-actions]

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

Targets: build

Platforms: linux/amd64

Image Tag: 47668f34b4eebcd868637b7ed239a809a1bb7cc8