Skip to content

Commit d4c278a

Browse files
authored
Merge pull request #199 from spaghetticode/spaghetticode/remove-release-doc
Point to Solidus wiki for gem release
2 parents 8ee0eeb + 3731fc7 commit d4c278a

1 file changed

Lines changed: 1 addition & 42 deletions

File tree

README.md

Lines changed: 1 addition & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -98,45 +98,4 @@ bundle exec rake
9898

9999
## Releasing a new version
100100

101-
#### 1. Bump gem version and push to RubyGems
102-
103-
We use [gem-release](https://github.com/svenfuchs/gem-release) to release this
104-
extension with ease.
105-
106-
Supposing you are on the master branch and you are working on a fork of this
107-
extension, `upstream` is the main remote and you have write access to it, you
108-
can simply run:
109-
110-
```bash
111-
gem bump --version minor --tag --release
112-
```
113-
114-
This command will:
115-
116-
- bump the gem version to the next minor (changing the `version.rb` file)
117-
- commit the change and push it to upstream master
118-
- create a git tag
119-
- push the tag to the upstream remote
120-
- release the new version on RubyGems
121-
122-
Or you can run these commands individually:
123-
124-
```bash
125-
gem bump --version minor
126-
gem tag
127-
gem release
128-
```
129-
130-
#### 2. Publish the updated CHANGELOG
131-
132-
After the release is done we can generate the updated CHANGELOG
133-
using
134-
[github-changelog-generator](https://github.com/github-changelog-generator/github-changelog-generator)
135-
by running the following command:
136-
137-
138-
```bash
139-
bundle exec github_changelog_generator solidusio/solidus_auth_devise --token YOUR_GITHUB_TOKEN
140-
git commit -am 'Update CHANGELOG'
141-
git push upstream master
142-
```
101+
Please refer to the dedicated [page](https://github.com/solidusio/solidus/wiki/How-to-release-extensions) on Solidus wiki.

0 commit comments

Comments
 (0)