It makes sense to check if a gem still builds within a PR. That ensures that an upcoming release isn't broken. At Vox Pupuli we use the following matrix:
Run gem builds with gem build --strict --verbose *.gemspec during each PR. The same should be applied for releasing a gem.
Describe Alternatives You've Considered
A clear and concise description of any alternative solutions or features you've considered.
Additional Context
This can be considered as a breaking change for gems without proper dependency boundaries. In those cases the command will fail with --strict. This change shouldn't be implemented in the main branch but rather in something like a v2. See https://github.com/puppetlabs/cat-github-actions/issues/89
thanks @bastelfreak! We agree this is a good change to have, and will help catch broken gem builds before they are merged. We have added this to the backlog.
Use Case
It makes sense to check if a gem still builds within a PR. That ensures that an upcoming release isn't broken. At Vox Pupuli we use the following matrix:
Describe the Solution You Would Like
Run gem builds with
gem build --strict --verbose *.gemspec
during each PR. The same should be applied for releasing a gem.Describe Alternatives You've Considered
A clear and concise description of any alternative solutions or features you've considered.
Additional Context
This can be considered as a breaking change for gems without proper dependency boundaries. In those cases the command will fail with
--strict
. This change shouldn't be implemented in the main branch but rather in something like a v2. See https://github.com/puppetlabs/cat-github-actions/issues/89