Skip to content

chore: back-merge main into develop (post cli 2.3.1)#133

Merged
samuelds merged 2 commits into
developfrom
chore/back-merge-main-2026-05-09-post-cli-2.3.1
May 9, 2026
Merged

chore: back-merge main into develop (post cli 2.3.1)#133
samuelds merged 2 commits into
developfrom
chore/back-merge-main-2026-05-09-post-cli-2.3.1

Conversation

@samuelds
Copy link
Copy Markdown
Contributor

@samuelds samuelds commented May 9, 2026

Summary

Back-merge curatif main → develop après le release sync de cli 2.3.1 (PR #132).

Why

Maintien de la divergence main↔develop à 0 après chaque sync, conformément au pattern établi (cf. PRs cli #125, #128, core #101, marketplace #221).

Bypass Check Changeset Present

Label skip-changeset ajouté. Justification : back-merge n'introduit aucun nouveau code à publier sur npm — c'est juste un sync des merge commits déjà sur main.

Test plan

  • CI passe
  • Pas de threads bots non-resolved
  • git log origin/develop..origin/main doit être vide après merge

🤖 Generated with Claude Code

samuelds and others added 2 commits May 9, 2026 01:04
Copilot AI review requested due to automatic review settings May 9, 2026 08:06
@samuelds samuelds added the skip-changeset PR does not require a changeset entry label May 9, 2026
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@samuelds samuelds enabled auto-merge May 9, 2026 08:06
@samuelds samuelds merged commit deafe7d into develop May 9, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset PR does not require a changeset entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants