Qovery
OSS
console
chore(release): reconcile main into staging (#2805) <!-- Thanks for contributing to the Qovery Console. Before opening the PR: - A JIRA ticket exists and you are assigned to it (unless it is a trivial fix) - Changes were tested locally (app and/or Storybook as relevant) - The code follows the rules under `.cursor/rules` --> ## Summary **Issue**: <!-- QOV-1234 --> <!-- Brief description of what this PR does --> <!-- step-by-step instructions for reviewers --> <!-- bullet list of changes --> <!-- reasons / problems solved --> <!-- highlight the key implementation details --> ## Screenshots / Recordings <!-- | Before | After | | ----------------------------------- | -------------------------- | | drag & drop image optional | drag & drop image | --> ## Testing - [ ] Changes tested locally in the relevant Console's pages and Storybooks - [ ] `yarn test` or `yarn test -u` (if you need to regenerate snapshots) - [ ] `yarn format` - [ ] `yarn lint` ## PR Checklist - [ ] I followed naming, styling, and TypeScript rules (see `.cursor/rules`) - [ ] I performed a self-review (diff inspected, dead code removed) - [ ] I titled the PR using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#commit-message-with-scope) with a scope when possible (e.g. `feat(service): add new Terraform service`) - required for semantic-release - [ ] I only kept necessary comments, written in English (watch for useless AI comments) - [ ] I involved a designer to validate UI changes if I am not a designer - [ ] I covered new business logic with tests (unit) - [ ] I confirmed CI is green (Codecov red can be accepted) - [ ] I reviewed and executed locally any AI-assisted code
nx e2e console-e2e
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx e2e console-e2e
Click to copy
Linux
4 CPU cores
read
access token used
d1900fd3
staging