gh-release

gh-release copied to clipboard

maybe change it from an error to a warning and allow either an empty body or use https://www.npmjs.com/package/string-editor

switch to warnings, e.g.

Warning: Missing CHANGELOG.md
Warning: Version mismatch (package.json, CHANGELOG.md)

@ungoldman 👋

Is this still active?

@jrmykolyn 👋

Yes! This would be a major (breaking) change, and requires a little consideration before implementing, but would be a great addition to current functionality.

My concern is avoiding breaking workflows for current users who rely on the current CLI's strictness to ensure deploys are successful.

Maybe hiding this behind a flag (like --force) would be a good (non-breaking) way to proceed for now? Open to your thoughts on this as well.

@ungoldman Hey hey. Sorry about the delay in responding to this.

Happy to help out if possible, although I think I need a deeper understanding of all the moving parts before I can offer anything of value. I'll dig into the internals and get back to you ASAP.

That said, your solution sounds like a good one!

Is this still a requested feature? Was thinking of implementing it bc we have a case where no changelog is necessary. Also was thinking of adding a way to auto advance the package version number and commit it so the entire process of bumping the release and releasing it can be automated.

I would still like to see it. Also, it would be nice if there was a skip release option, for when you use a gh-release hook in the release nom script. Sometimes you already gh-released and just need to skip interactively.

I ended up using release-it since it did everything I needed out of the box. If I free up again and have a need for a smaller release lib I'll look at it again thanks.