Skip to content

build(2.2.2): merge release into main#190

Merged
Phil91 merged 2 commits intomainfrom
release/v2.2.3
Jun 4, 2025
Merged

build(2.2.2): merge release into main#190
Phil91 merged 2 commits intomainfrom
release/v2.2.3

Conversation

@Phil91
Copy link
Copy Markdown
Collaborator

@Phil91 Phil91 commented Jun 4, 2025

Description

merge the latest changes into the main branch

Why

to have the latest changes in the main branch

Issue

N/A

Checklist

  • I have performed a self-review of my own code
  • I have successfully tested my changes locally
  • I have added tests that prove my changes work
  • I have checked that new and existing tests pass locally with my changes
  • I have commented my code, particularly in hard-to-understand areas
  • I have added copyright and license headers, footers (for .md files) or files (for images)

github-actions Bot and others added 2 commits June 4, 2025 15:18
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Reviewed-by: Phil Schneider <info@philschneider.de>
@Phil91 Phil91 changed the title chore: merge release into main build(2.2.2): merge release into main Jun 4, 2025
@Phil91 Phil91 merged commit 48867fe into main Jun 4, 2025
9 checks passed
@Phil91 Phil91 deleted the release/v2.2.3 branch June 4, 2025 13:33
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.

1 participant