-
-
Notifications
You must be signed in to change notification settings - Fork 280
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 for version 3.0.0 of the spec #759
Conversation
/au |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
I don't get why we are having those conflicts here. I expect these merges to apply without conflicts as there are no changes in this branch either. |
I wonder why this PR is having conflicts. I was looking at the changes in #807 and they all seem pretty straightforward to auto-merge for git but for some reason, it's not doing it. |
There are changes. In this branch, for instance, the examples are already "migrated" to version 3.0.0 and the spec already has the version number updated too. Still not enough to get this amount of conflicts IMO but worth mentioning. |
Oh, yeah I didn't notice. Thanks for mentioning it. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@jonaslagoni fyi there are many merge conflicts. Because of this, the bot cannot keep it up to date with |
Let me have a look. I'm gonna rebase and cherry-pick to try to clean the history. Let's see if it works. |
Alright, so I think I found the problem (or at least the PR that's causing the majority of them). #753 is changing a lot of files replacing |
8805c88
to
624ad52
Compare
Co-authored-by: Sergio Moya <[email protected]>%0ACo-authored-by: Jonas Lagoni <[email protected]>%0ACo-authored-by: [email protected] <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
chore: update with master
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Because of this issue, we need to manually merge this PR if we want to keep mentions to the co-authors of this PR. So please, when merging, add the following commit message description literally (with the two empty lines at the beginning as well):
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This PR is created upfront to reflect on a daily basis what things are included in the release.
Also, the reason to create this PR a long time before the release is to enable automation (bot keeps upstream branches always up to date with master, see this action) that we have in place to regularly update the release branch with whatever is changed in the master branch. So nobody has to do it manually.
TO DO: