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: version 5.0.0-rc0001 #127

Merged
merged 19 commits into from
Jul 8, 2024
Merged

release: version 5.0.0-rc0001 #127

merged 19 commits into from
Jul 8, 2024

Conversation

domire8
Copy link
Member

@domire8 domire8 commented Jul 8, 2024

Description

Thanks to #126, if I forward this onto main, it should build and release modulo as v5.0.0-rc0001 and rolling such that we can continue with the refactors throughout the stack.

Review guidelines

Estimated Time of Review: 2 minutes

Checklist before merging:

  • Confirm that the relevant changelog(s) are up-to-date in case of any user-facing changes

… to CL v8.1.0 (#106)

* feat: remove utilities header from modulo controllers

* feat: throw exception on get parameter

* feat: use cl 8.1.0
* refactor: change predicate topic of controllers

* docs: changelog
* feat(components): only publish predicate on change (cpp)

* feat(components): only publish predicate on change (py)

* feat: add unittests for predicate class

* fix: triggers
@domire8 domire8 requested a review from eeberhard July 8, 2024 12:03
@domire8
Copy link
Member Author

domire8 commented Jul 8, 2024

I've also built and run a full jazzy backend with this version now and seems to work fine so far

@eeberhard
Copy link
Member

🚂 🔥

This is a great moment! Lots of hard work behind the scenes. Let's go for it with the breaking changes on main, with the pre-release tag there to make sure we can patch anything before fully committing to 5.0.

I assume the merge strategy will be to fast-forward the commits to main.

@domire8 domire8 merged commit 4d5a826 into main Jul 8, 2024
4 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jul 8, 2024
@domire8 domire8 deleted the breaking branch July 8, 2024 15:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants