remove supertokens-core and supertokens-node

[n1ru4l]

This PR enabled the native supertokens implementation, by updating the relevant docker compose files and checks if CI and e2e tests pass against it.

[gemini-code-assist]

Summary of Changes

Hello @n1ru4l, 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 focuses on refining the integration test environment by correctly configuring the SuperTokens authentication service. The changes involve enabling a specific 'home' mode for SuperTokens and supplying essential token keys, which are critical for the authentication and authorization processes during automated test execution. This ensures that integration tests can run reliably and securely.

Highlights

• SuperTokens Configuration: Configured SuperTokens environment variables to ensure proper functionality within the integration testing setup.
• Integration Test Environment: Enabled the SUPERTOKENS_AT_HOME flag, indicating a specific mode for SuperTokens operation in the integration test environment.
• Authentication Keys: Provided the necessary SUPERTOKENS_REFRESH_TOKEN_KEY and SUPERTOKENS_ACCESS_TOKEN_KEY to the graphql-engine service for secure token handling during tests.

Changelog

• integration-tests/.env
  • Updated the SUPERTOKENS_AT_HOME environment variable from 0 to 1.
• integration-tests/docker-compose.integration.yaml
  • Added SUPERTOKENS_AT_HOME with a value of 1 to the graphql-engine service environment.
  • Included SUPERTOKENS_REFRESH_TOKEN and SUPERTOKENS_ACCESS_TOKEN_KEY environment variables for the graphql-engine service.

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 (alpha)

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

Package	Version	Info
hive	10.0.0-alpha-20260225134236-1e0cd7e1502576f576213f914017e48126913856	npm ↗︎ unpkg ↗︎

[gemini-code-assist]

Code Review

This pull request enables the supertokens-at-home feature for integration tests by setting the SUPERTOKENS_AT_HOME environment variable to 1 and adding the required token keys to the docker-compose.integration.yaml configuration. My review identifies a likely typo in an environment variable name which could cause issues.

[github-actions]

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

Targets: build

Platforms: linux/amd64

Image Tag: 1e0cd7e1502576f576213f914017e48126913856

[github-actions]

💻 Website Preview

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