Bake Modernize

A gem for modernizing files in your Ruby project.

Please see the project documentation for more details.

• Getting Started - This guide explains how to update a Ruby gem with bake-modernize, review the generated changes, and optionally migrate to releases through GitHub.

Please see the project releases for all releases.

• Remove certificate signing tasks and gemspec settings. GitHub releases use Trusted Publishing and attestations without a separate RubyGems signing key.

• Prefer the configured signing owner or GitHub owner when selecting RubyGems signing certificates and private keys.

• Refresh license.md and Ruby copyright headers with modernize:license after version increments in generated release hooks.

• Provide agent context for updating gems and configuring GitHub releases.
• Ignore [bot] authors in copyright attributions and gem authors.
• Add opt-in modernize:releases:github migration and omit redundant publishing hooks for gems using bake-gem-github.

• Ignore /vendor/bundle by default for dependencies installed by GitHub Actions' Bundler cache.

• Better version.rb detection in modernize:gemspec.

• Make modernize:releases part of the default modernize task.

• Add support for automatic GitHub release generation.

• Improved copilot instructions for using agent context.

• Add modernize:releases to add release notes.

We welcome contributions to this project.

1. Fork the repository.
2. Create your feature branch (git checkout -b my-new-feature).
3. Commit your changes (git commit -am 'Add some feature.').
4. Push to the branch (git push origin my-new-feature).
5. Create a new pull request.

To run the test suite:

$ bundle exec sus

To prepare a release branch and open a pull request from an up-to-date main:

$ bundle exec bake gem:github:release:patch # or minor or major

See bake-gem-github for setup, remote releases, and recovery.

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.