Skip to content

Main2Dev @W-21503929@ Merging main to dev after v5.10.2#2005

Merged
aruntyagiTutu merged 2 commits intodevfrom
m2d/v5.10.2
Mar 9, 2026
Merged

Main2Dev @W-21503929@ Merging main to dev after v5.10.2#2005
aruntyagiTutu merged 2 commits intodevfrom
m2d/v5.10.2

Conversation

@svc-cli-bot
Copy link
Contributor

@svc-cli-bot svc-cli-bot commented Mar 9, 2026

This branch and PR were automatically created following the successful release of v5.10.2.
It must be MERGED into dev, NOT SQUASHED OR REBASED. Squashing or rebasing this branch onto dev can cause potentially irreconcilable merge conflicts later.
As an additional safeguard and reminder, the title of this PR MUST include the word 'merging' in the description portion of the PR title, e.g., 'Main2Dev @W-21503929@ Merging main to dev after v5.10.2'.
If there are conflicts between dev and this branch, you should do the following locally:

  • $ git checkout dev
  • $ git pull
  • $ git fetch --all
  • $ git checkout m2d/v5.10.2
  • $ git pull origin dev --no-rebase # You MUST include this flag, or someone's day will be ruined.
  • Resolve the merge conflicts manually. When in doubt, ask the code's author for help.
  • $ git commit
  • $ git push

github-actions bot and others added 2 commits March 9, 2026 05:53
@aruntyagiTutu aruntyagiTutu changed the title Filler title. Read description and rename. Main2Dev @W-21503929@ Merging main to dev after v5.10.2 Mar 9, 2026
@aruntyagiTutu aruntyagiTutu merged commit 8060c2b into dev Mar 9, 2026
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants