Request: release info about node-red-contrib-simple-gate

[drmibell]

I will look into this. It would involve publishing GitHub releases, which is something I have not done before. Contributing Node-RED nodes is strictly a hobby for me, and since I began with absolutely no knowledge of git or npm, there has been a fairly steep learning curve.

[colinl]

Hi Michael. I do this with my nodes. It is very easy and I think worthwhile. These are my notes on how to do it. I always make notes about things that I don't do every day.

Releasing a new version release on github:
Having committed and pushed to github (not tagged), click on Code, then Create a new release (under Releases in the right hand panel) then Draft a new Release
Fill in a tag name (eg v1.0.1) title (eg Version 1.0.1) and description and Publish
Pull local repo to pickup tag

Then you end up with something like this https://github.com/colinl/node-red-contrib-pid/releases

Edit: The above adds a tag to the current version on github. If you wanted to do it retrospectively you would have to get to the appropriate version first, I would have to look up how to do that.

[drmibell]

Thanks, Colin. Seems simple enough (with your notes). Do you think it's worth trying to do retrospectively? I keep a CHANGELOG.md in the repo that is kind of bare bones but could serve for hindsight.

[colinl]

I wouldn't bother myself. I think to tag a release retrospectively you have to check out the revision you want locally and apply the tag there, and push it to github. Then on github you can select that tag to apply the release to. All a bit of a faff.

[drmibell]

Thanks for looking into this. It doesn't seem worth the effort for older versions. When I get time, I'll have a go at the current versions of my nodes to see if I can get the hang of it.

[drmibell]

I have generated release notes for version 0.5.2 and will do the same for future versions.