chore: add openai env to smokeTests

[wtfsayo]

Reverts #2459

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request modifies the GitHub Actions workflow for smoke tests, focusing on enhancing the dependency management and caching strategy. The workflow now uses a Node.js 23 container and implements a more robust caching mechanism for pnpm dependencies. The changes aim to optimize the CI/CD process by explicitly defining cache paths and utilizing the latest caching action.

Changes

File	Change Summary
.github/workflows/smoke-tests.yml	- Added node:23-bullseye container specification - Replaced pnpm caching with actions/cache@v4 - Specified cache paths for ~/.pnpm-store and node_modules - Created cache key using OS and pnpm-lock.yaml hash - Renamed pnpm setup step

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/smoke-tests.yml (1)

18-25: Optimize cache configuration

The caching strategy could be improved:

1. Consider caching only the root node_modules
2. Add more specific restore-keys for better fallback

  path: |
    ~/.pnpm-store
-   **/node_modules
+   node_modules
  key: ${{ runner.os }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
  restore-keys: |
    ${{ runner.os }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
    ${{ runner.os }}-pnpm-

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1214de8 and 88af7a7.

📒 Files selected for processing (1)

• .github/workflows/smoke-tests.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: integration-tests
• GitHub Check: smoke-tests

🔇 Additional comments (2)

.github/workflows/smoke-tests.yml (2)

13-14: Consider using Node.js LTS version

Node.js 23 is not an LTS release and will reach EOL in June 2024. Consider using node:20-bullseye for better stability.

---

27-30: Verify pnpm version compatibility

The pinned pnpm version looks good, but let's verify it matches project requirements.

[twilwa]

i did this if i broke everything its my fault