Automate releasing #23
Description
Right now, it's me manually pulling and running rake release. Ideally, this happens automatically on main when the gemspec version changes, or if it is manually run.
Tried this, but without luck so far:
It is currently failing with:
singed 0.2.2 built to pkg/singed-0.2.2.gem.
rake aborted!
There are files that need to be committed first.
/home/runner/work/singed/singed/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/opt/hostedtoolcache/Ruby/3.1.4/x64/bin/bundle:25:in `load'
/opt/hostedtoolcache/Ruby/3.1.4/x64/bin/bundle:25:in `<main>'
Tasks: TOP => release => release:guard_clean
(See full trace by running task with --trace)
I thought it could be the cache step, but I've added vendor/bundler to .gitignore . It's unfortunate it doesn't tell you what is uncommitted.
My next thought is to add a git status to the build, but that might not trigger in the right place. If that doesn't show it, then I think it's a matter of adding rake tasks to do git status before various steps 🤔