Contribution to Deprecation Toolkit

Releasing a new version

Audit PRs and commits merged since the last release, ensuring all user fancing changes are documented in CHANGELOG.md.
Based on the changes, determine whether to increment the major, minor, or patch version, adhering to Semantic Versioning.
Update the gem version string accordingly in lib/deprecation_toolkit/version.rb.
Run bundle install to update the Gemfile.lock.
Insert a new heading in CHANGELOG.md containing the version identifier and expected release date (e.g. ## 1.2.3 (1999-12-31)).
Commit changes on a new branch and open a PR.
Draft a new release on GitHub, but do not publish it yet.
Once you have received approval on your PR, merge it into main.
Deploy using the ShipIt UI, and verify the new version is available on RubyGems.
Publish the drafted release, tagging the deployed commit (should be HEAD of the main branch) with a tag of the form vMAJOR.MINOR.PATCH.

If something goes wrong during the deploy process, address it and tag whatever commit was successfully deployed as that version.