Skip to content

Conversation

@juliusknorr
Copy link
Contributor

@juliusknorr juliusknorr commented Aug 11, 2022

💥 Breaking Change

🚀 Enhancement

🐛 Bug Fix

Signed-off-by: Julius Härtl <[email protected]>
@juliusknorr juliusknorr force-pushed the release/v6.0.0-beta.1 branch from b267f91 to 894bae5 Compare August 11, 2022 06:28
@skjnldsv skjnldsv merged commit 71468d3 into master Aug 11, 2022
@skjnldsv skjnldsv deleted the release/v6.0.0-beta.1 branch August 11, 2022 06:39
@skjnldsv
Copy link
Contributor

@skjnldsv
Copy link
Contributor

@nickvergessen
Copy link
Contributor

Error: API rate limit exceeded for installation ID 1183434.

Oo

@skjnldsv
Copy link
Contributor

Manually published

@raimund-schluessler
Copy link
Contributor

I think the changelog anyway needs a bit of manual work for the final 6.0.0 release to point out breaking changes and maybe help with the migration.

And we shouldn't forget to create a stable6 branch on release, I guess.

@skjnldsv
Copy link
Contributor

And we shouldn't forget to create a stable6 branch on release, I guess.

We only did that when starting the next major.
Master can stay 6.x.x until we need to merge a breaking change, then we branch off

@raimund-schluessler
Copy link
Contributor

And we shouldn't forget to create a stable6 branch on release, I guess.

We only did that when starting the next major. Master can stay 6.x.x until we need to merge a breaking change, then we branch off

Ok, I just hope, we don't forget 🙈

@skjnldsv
Copy link
Contributor

Ok, I just hope, we don't forget

We can always branch off after a breaking change is merged, you can branch off from a specific commit! 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants