Skip to content

fix(release): use merge commits for production promotion#2802

Merged
RemiBonnet merged 1 commit into
stagingfrom
fix/release-promotion-branch
Jul 7, 2026
Merged

fix(release): use merge commits for production promotion#2802
RemiBonnet merged 1 commit into
stagingfrom
fix/release-promotion-branch

Conversation

@RemiBonnet

Copy link
Copy Markdown
Member

Summary

Issue:

Screenshots / Recordings

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 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

@RemiBonnet RemiBonnet marked this pull request as ready for review July 7, 2026 10:31
@RemiBonnet RemiBonnet merged commit 07531f2 into staging Jul 7, 2026
11 checks passed
@RemiBonnet RemiBonnet deleted the fix/release-promotion-branch branch July 7, 2026 12:02
@RemiBonnet

Copy link
Copy Markdown
Member Author

🎉 This PR is included in version 1.326.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants