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

Release v1.1.0 #668

Merged
merged 2 commits into from
Nov 14, 2023
Merged

Release v1.1.0 #668

merged 2 commits into from
Nov 14, 2023

Conversation

EtienneLt
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem?

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change or deprecate an API?

  • The Breaking Change or Deprecated label has been added
  • The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

@EtienneLt EtienneLt changed the title Release v1.1.0 [WIP] Release v1.1.0 Oct 25, 2023
@EtienneLt
Copy link
Contributor Author

Waiting for open reac upgrade

Signed-off-by: Etienne LESOT <[email protected]>
Signed-off-by: Etienne LESOT <[email protected]>
@EtienneLt EtienneLt changed the title [WIP] Release v1.1.0 Release v1.1.0 Nov 14, 2023
@EtienneLt EtienneLt merged commit e7823f8 into main Nov 14, 2023
7 checks passed
@EtienneLt EtienneLt deleted the release-v1.1.0 branch November 14, 2023 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants