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

Prepare v2.8.0 release #135

Merged
merged 2 commits into from
Jan 31, 2024
Merged

Prepare v2.8.0 release #135

merged 2 commits into from
Jan 31, 2024

Conversation

olperr1
Copy link
Member

@olperr1 olperr1 commented Jan 31, 2024

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines

What kind of change does this PR introduce?
Prepare next release 2.8.0

What is the current behavior?
2.8.0-SNAPSHOT version

What is the new behavior (if this is a feature change)?
2.8.0 (first commit) then 2.9.0-SNAPSHOT (2nd commit)

Other information:
⚠️ DO NOT squash the commits
⚠️ Merge branch on main with fast-forward locally, then push, in order to keep the commits verified

Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
@olperr1 olperr1 requested a review from So-Fras January 31, 2024 14:29
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@olperr1 olperr1 merged commit 3641ea3 into main Jan 31, 2024
6 checks passed
@olperr1 olperr1 deleted the tmp_prepare_release branch January 31, 2024 14:40
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