Skip to content

Add MIT license - #22

Merged
dduugg merged 1 commit into
mainfrom
add-mit-license
Sep 30, 2026
Merged

dduugg merged 1 commit into
mainfrom
add-mit-license

Conversation

@dduugg

@dduugg dduugg commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Adds an MIT LICENSE ("Copyright (c) 2022 Gusto"). The text is identical to code_ownership, code_teams, packs, gem_template, and the other rubyatscale gems. The year matches this repo's first commit, 2022-09-15.
  • Declares spec.license = "MIT" in the gemspec and adds LICENSE to spec.files, so the notice ships inside the packaged gem as MIT requires.
  • Adds a ## License section to the README.
  • Bumps the version to 1.9.1 (and updates Gemfile.lock) so the license metadata reaches rubygems.org. The published 1.9.0 has an empty license field.

Test plan

  • gem build reports licenses: [MIT], the packaged file list includes LICENSE, and the "licenses is empty" build warning is gone
  • bundle exec rspec passes locally (19 examples, 0 failures)
  • rubyfmt --check passes locally
  • Local Fresh Eyes review: no findings
  • CI passes on this PR

The repo and published gem carried no license. Add the same MIT LICENSE
used by the other rubyatscale gems, declare it in the gemspec, and ship
the LICENSE file in the packaged gem as MIT requires. Bump to 1.9.1 so
the license metadata reaches rubygems.org.
@dduugg
dduugg requested a review from a team as a code owner September 30, 2026 20:41
@dduugg
dduugg merged commit 1ece0c7 into main Sep 30, 2026
9 checks passed
@dduugg
dduugg deleted the add-mit-license branch September 30, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant