Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

build(2.2.0): merge release into main #157

Merged
merged 3 commits into from
Feb 7, 2025
Merged

build(2.2.0): merge release into main #157

merged 3 commits into from
Feb 7, 2025

Conversation

Phil91
Copy link
Collaborator

@Phil91 Phil91 commented Feb 7, 2025

Description

merge the latest release into main

Why

To have the latest changes of the release 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)

Phil91 and others added 2 commits February 7, 2025 14:41
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@Phil91 Phil91 requested a review from evegufy February 7, 2025 14:08
CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Evelyn Gurschler <evelyn.gurschler@bmw.de>
@Phil91 Phil91 merged commit f6a3c59 into main Feb 7, 2025
8 checks passed
@Phil91 Phil91 deleted the release/v2.2.0 branch February 7, 2025 14:24
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants