chore: update inbound env key

[ElasticBottle]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @ElasticBottle, 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 addresses a routine maintenance task by updating an encrypted environment variable in the production configuration. The change ensures that the application utilizes the correct and most current key for SEO inbound API operations, maintaining operational integrity.

Highlights

• Environment Variable Update: The SEO_INBOUND_API_KEY in the .env.production file has been updated with a new encrypted value.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .env.production
  • Updated the SEO_INBOUND_API_KEY with a new encrypted value.

Activity

• No specific activity (comments, reviews, etc.) has been recorded for 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the SEO_INBOUND_API_KEY in the production environment. While this appears to be a routine secret rotation, I've noticed that this environment variable is not declared in the environment validation schemas provided in the context. This could lead to runtime issues if the application relies on this key. I've left a comment with a suggestion to add it to the schema for better type safety and maintainability.

[gemini-code-assist]

The environment variable SEO_INBOUND_API_KEY is being updated, but it doesn't appear to be defined in any of the environment validation schemas (e.g., in packages/api-seo/src/env.ts). This could mean the variable is not being used, or it's being accessed without validation, which could lead to runtime errors in production.

To ensure this variable is correctly validated and accessible throughout the application, please consider adding it to the server-side environment schema in packages/api-seo/src/env.ts:

// packages/api-seo/src/env.ts
export const apiEnv = () =>
  createEnv({
    // ...
    server: {
      // ...
      SEO_INBOUND_API_KEY: type("string"),
      // ...
    },
    // ...
  });

If this variable is intentionally not part of the schema or is defined in a file not included in the context, please ignore this comment. However, for maintainability and type safety, it's highly recommended to declare all environment variables.

[Copilot]

Pull request overview

This PR performs a routine credential rotation by updating the encrypted value of the SEO_INBOUND_API_KEY environment variable in the production environment file. This API key is used by the Inbound email service for sending transactional emails through the authentication system.

Changes:

• Updated the encrypted value of SEO_INBOUND_API_KEY in .env.production

[pkg-pr-new]

Open in StackBlitz

pnpm add https://pkg.pr.new/rectangular-labs/monorepo/@rectangular-labs/emails@395

pnpm add https://pkg.pr.new/rectangular-labs/monorepo/@rectangular-labs/loro-file-system@395

pnpm add https://pkg.pr.new/rectangular-labs/monorepo/@rectangular-labs/result@395

commit: ce40d97

[github-actions]

Cloudflare Preview URL for WWW 🎈 : https://pr-395.rectangularlabs.com (custom domain)
Cloudflare Preview URL for SEO 🎈 : https://pr-395.fluidposts.com (custom domain)
Cloudflare Preview URL for SEO WWW 🎈 : https://www-pr-395.fluidposts.com (custom domain)
Cloudflare Preview URL for SEO Contact 🎈 : https://contact-pr-395.fluidposts.com (custom domain)