danger-samsao 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 608978c81f0415647bdf2a56bd87899397eccfca
-  data.tar.gz: 82332e9016b7efe03cee778b5fd43150cc494037
+  metadata.gz: ce381ca0181a3c9df3c2c536e6d707bce6defcbe
+  data.tar.gz: 14d687d8d21fb34fd864526eb1fd82832b0835cd
 SHA512:
-  metadata.gz: c80089389404b1c748ba22e14621e77af2ac1f6de1c56b0202b75b35700b58d59def8ee0c4afb6a9ce88bb88bfb9c759388290c78f0b106a423363a9d96ae3ab
-  data.tar.gz: b84adde8c6cb832fcdc00b769ba088a002a37c0237e78bab75ea7bc0a26ef14fa4ab17af8f12b38d195622c6cd4ce91f344d88a9436f6e881b65136059ff9f77
+  metadata.gz: c73357ebc4b5683b292f389f08e810fb5467997bddbcc6c5b6bc27250c8b659b822de6a7d36106e5392b292d29fe8d8f516f20877028ee523407054e291a6695
+  data.tar.gz: 00bec8ce51b8b01b75a3d2b9ee6fe5fab5a550b1763714eea63a2386837be29a85182b558b3ec01bbc9e20d581be1b096b08507638114e0095ea2cc24750c68b

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.1.1 (May 4, 2017)
+
+ * Open source to MIT.
+
 ## 0.1.0 (May 1, 2017)
 
  * Added `fail_when_merge_commit_detected` action.

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    danger-samsao (0.1.0)
+    danger-samsao (0.1.1)
       danger-plugin-api (~> 1.0)
 
 GEM

data/README.md

@@ -228,3 +228,63 @@ and enter the token to the side of `DANGER_GITHUB_API_TOKEN` line.
 
 The release process is quite simple. It consists of doing a release commit,
 run a rake task and finally doing a bump to next version commit and push it.
+Assume for the rest of this section that we are releasing version `0.1.0`
+and today's date is `May 1st, 2017`. Terminal commands are given, but feel
+free to use `SourceTree` or anything else.
+
+Start by checking out the commit that was flagged as the release commit (could be
+the `develop` branch) and name the branch `release/0.1.0`:
+
+```
+git checkout -b release/0.1.0 aeb156fb4a
+```
+
+Once on the branch, modify `CHANGELOG.md` so that `In progress` is replaced by
+the current version and released date `## 0.1.0 (May 1, 2017)`. Then modify
+`lib/samsao/gem_version.rb` to ensure the version is set to current value
+`VERSION = '0.1.0'.freeze`. Lastly, run `bundle install` just to ensure
+`Gemfile.lock` has correct new version also.
+
+With all these changes, make a release commit and use the following normalized
+text as the commit message:
+
+```
+Released version 0.1.0
+```
+
+Once the commit is done, simply run `bundle exec rake release`. This will
+ask you for the Samsao's RubyGems credentials (only if it's your first
+release, ask a system administrator to get them). It will create a tag
+on the current commit of the current branch (should be the release commit
+made earlier) named `v0.1.0`. And it will finally push the tag to the
+repository as well as building and publishing the gem on RubyGems.
+
+Last thing to do is bumping to next development version. Edit back
+`CHANGELOG.md` so that `## In progress` is the new section header and
+add a bunch of empty lines (around 10, only 2 shown in the example for
+brevity) starting with a **space** followed by a **star**:
+
+```
+## In progress
+
+ *
+
+ *
+
+## 0.1.0 (May 1, 2017)
+```
+
+Also edit `lib/samsao/gem_version.rb` so that next development version
+value is used `VERSION = '0.1.1.pre1'.freeze`. The `.pre1` is the lowest
+possible version before the official `0.1.1` one (or higher).
+
+Commit all this changes together in a new commit that has the following
+message:
+
+```
+Bumped to next development version
+```
+
+Finally, create a PR with this branch and open a pull request and merge
+right away (your team mates should known in advance that a release is
+happening and branch merged faster than other ones).

data/lib/samsao/gem_version.rb

@@ -1,3 +1,3 @@
 module Samsao
-  VERSION = '0.1.0'.freeze
+  VERSION = '0.1.1'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: danger-samsao
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Samsao Development Inc.