Add breaking changes to GitHub release notes

[oprogramador]

The release notes on GitHub are currently empty. It would be beneficial if these contained the breaking changes for each major release. Currently these are only showing in the github repo.

This is about hooking into the release scripts and pushing the changes to the Github releases using the Github API. Start by investigating how the release script works by looking at the scripts in package.json and then how to extract the relevant parts from the changelog markdown file. The github API is quite easy to grok.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[oprogramador]

IMO stale bot doesn't work correctly. The issue could be closed if I get an answer and there's a lack of activity on my side but not in this case when I've got no answer.

[mroderick]

IMO stale bot doesn't work correctly. The issue could be closed if I get an answer and there's a lack of activity on my side but not in this case when I've got no answer.

I agree. stale-bot is not quite there yet.

I've added the "pinned" label, which means that stale-bot should leave it alone. Let's see how it goes :)

[rnd-debug]

Hello. I would like to contribute, but is this open for external contributions?
I assume that:

• this issue requires to update CHANGELOG.md ?
• the needed info is to be found in docs/guides/migrating-to-X.0.md ?

[fatso83]

@rnd-debug that seems correct. And every file is open for contributions 🙂

Just try and build the webpage first, and then things hopefully starts making sense 👍

[rnd-debug]

@fatso83 sorry, but i am still confused. I went quickly through the docs/guides/migrating-to-X.0.md and it seems to me that everything from those files is already mentioned in the ROOT/CHANGELOG.md.
So is the task actually about:

• updating the sinon's homepage view (https://sinonjs.org/releases/) ?
• OR updating the git view ? => almost sure that normal contributors don't have access to this.

[fatso83]

The releases page is generated. You don't have to do anything there. And so the "git view". That is just an overview of the tags. Just have a look at the source code for the releases page and it should be apparent.

[fatso83]

Ah, sorry, I have been misled about what this concerns. I read your initial questions and thought it actually had to do with the homepage releases. After pressing the link in the issue description I see that this has nothing to do with the home page at all!

This is about hooking into the release scripts and pushing the changes to the Github releases using the Github API. Something very different indeed 😃 Start by investigating how this works by looking at the scripts in package.json and then how to extract the relevant parts from the changelog. The github API is quite easy to grok at least.

[fatso83]

Editing the description of this to reflect what is needed to be done.