feat(ci): use APP_ENV variable for generateConfig in CI

[PierreBrisorgueil]

Summary

• Add NODE_ENV: ${{ vars.APP_ENV || 'development' }} to the generateConfig step so downstream projects can load their own config file via a repo variable
• Update E2E Vue dev server step to use ${{ vars.APP_ENV || 'test' }} instead of hardcoded test
• Zero breaking change — defaults preserve current behavior

Closes #3795

Test plan

• CI passes on this PR (devkit defaults to development/test)
• Downstream project with APP_ENV repo variable picks up correct config

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow configuration to support flexible environment settings during the build and testing processes.

[coderabbitai]

Warning

Rate limit exceeded

@PierreBrisorgueil has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 7 minutes and 7 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 7 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5d379f80-e6e1-49b3-80f1-7b008cafaa6b

📥 Commits

Reviewing files that changed from the base of the PR and between 5085218 and b1ae04d.

📒 Files selected for processing (1)

• .github/workflows/CI.yml

Walkthrough

The CI workflow is updated to support configurable environment variables via repository variables. The npm run generateConfig step now sets NODE_ENV to ${{ vars.APP_ENV || 'development' }}, and the Vue dev server startup in the e2e job changes NODE_ENV from hardcoded test to ${{ vars.APP_ENV || 'test' }}, allowing downstream projects to override the runtime environment.

Changes

Cohort / File(s)	Summary
CI Workflow Configuration .github/workflows/CI.yml	Added NODE_ENV environment variable configuration using APP_ENV repository variable with fallback defaults for both the generateConfig step (development) and e2e Vue dev server step (test).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• #3795: Directly addresses the implementation of APP_ENV variable support for configurable NODE_ENV in CI generateConfig and e2e steps.

Suggested labels

Feat

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title clearly and concisely describes the main change: adding APP_ENV variable support to the generateConfig step in CI workflow.
Description check	✅ Passed	Description covers the key changes, rationale (zero breaking change with defaults), linked issue, and test plan, though missing some template sections like validation and guardrails.
Linked Issues check	✅ Passed	Changes fully implement requirements from #3795: NODE_ENV set with APP_ENV variable support in generateConfig step with development default, and E2E step updated to use APP_ENV with test fallback.
Out of Scope Changes check	✅ Passed	All changes in CI.yml are directly within scope of #3795 objectives; only NODE_ENV configuration for generateConfig and E2E steps modified as intended.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/ci-app-env

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.23%. Comparing base (1151d02) to head (b1ae04d).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3801   +/-   ##
=======================================
  Coverage   99.23%   99.23%           
=======================================
  Files          28       28           
  Lines         910      910           
  Branches      243      243           
=======================================
  Hits          903      903           
  Misses          7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/CI.yml:
- Line 109: Replace the shared APP_ENV fallback for E2E with a dedicated
override so E2E runs don't accidentally inherit repo-level APP_ENV: change the
NODE_ENV assignment to prefer a new vars.E2E_APP_ENV, then fall back to
vars.APP_ENV, then to 'test' (i.e., use vars.E2E_APP_ENV || vars.APP_ENV ||
'test'); update any workflow documentation or variable definitions to mention
vars.E2E_APP_ENV so maintainers can set E2E-specific environment without
altering APP_ENV.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 60c9a999-f6b8-4865-a3c5-66f99bc08813

📥 Commits

Reviewing files that changed from the base of the PR and between 8b4dd60 and 5085218.

📒 Files selected for processing (1)

• .github/workflows/CI.yml

[Copilot]

Pull request overview

Updates the CI workflow so downstream repositories can select which src/config/defaults/<env>.config.js file generateConfig uses by setting a repo variable (APP_ENV), without editing the workflow.

Changes:

• Set NODE_ENV from ${{ vars.APP_ENV || 'development' }} for the npm run generateConfig CI step.
• Set the E2E job’s Vue dev server NODE_ENV from ${{ vars.APP_ENV || 'test' }} instead of hardcoding test.