Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

feat: release v11.2.0 #223

Merged
merged 5 commits into from
Dec 12, 2024
Merged

feat: release v11.2.0 #223

merged 5 commits into from
Dec 12, 2024

Conversation

Duologic
Copy link
Member

@Duologic Duologic commented Sep 24, 2024

Title says it.

Most notable change is that the Team object is no longer part of the spec. I think we can merge without and fix later.

Base automatically changed from duologic/v11.1.0 to main October 1, 2024 13:19
@Duologic Duologic marked this pull request as ready for review December 10, 2024 10:14
@Duologic Duologic requested a review from a team as a code owner December 10, 2024 10:14
@Duologic Duologic mentioned this pull request Dec 10, 2024
@Duologic Duologic enabled auto-merge (squash) December 12, 2024 08:44
Copy link

@nikimanoledaki nikimanoledaki left a comment

Choose a reason for hiding this comment

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

LGTM 👍

How do we communicate & handle these breaking changes downstream? Release notes could be one way 🤔

@Duologic Duologic merged commit 537e6d6 into main Dec 12, 2024
2 checks passed
@Duologic Duologic deleted the duologic/v11.2.0 branch December 12, 2024 09:23
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