Sha256: 5fa9542bb17411ec5b891043364fe146eb0560e4ae3f03ee494c9421beccda7d
Contents?: true
Size: 1.42 KB
Versions: 2
Compression:
Stored size: 1.42 KB
Contents
# Releasing createsend-ruby ## Requirements - You must have a [RubyGems.org](https://rubygems.org/) account and must be an owner of the [createsend](https://rubygems.org/gems/createsend) gem. Owners can be added to the `createsend` gem like this: ``` gem owner createsend -a newowner@example.com ``` ## Prepare the release - Increment the `VERSION` constant in the `lib/createsend/version.rb` file, ensuring that you use [Semantic Versioning](http://semver.org/). - Add an entry to `HISTORY.md` which clearly explains the new release. - Ensure that the `Gemfile.lock` file is updated correctly by running: ``` bundle install ``` - Commit your changes: ``` git commit -am "Version X.Y.Z" ``` - Tag the new version: ``` git tag -a vX.Y.Z -m "Version X.Y.Z" ``` - Push your changes to GitHub, including the tag you just created: ``` git push origin master --tags ``` - Ensure that all [tests](https://travis-ci.org/campaignmonitor/createsend-ruby) pass, and that [coverage](https://coveralls.io/r/campaignmonitor/createsend-ruby) is maintained or improved. ## Build the gem ``` rake build ``` This builds the gem locally to a file named something like `createsend-X.Y.Z.gem`. You're now ready to release the gem. ## Release the gem ``` rake release ``` This publishes the gem to [RubyGems.org](https://rubygems.org/gems/createsend). You should see the newly published version of the gem there. All done!
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
createsend-3.4.0 | RELEASE.md |
createsend-3.3.0 | RELEASE.md |