Skip to content

Commit

Permalink
Preparing the new v0.0.2 release
Browse files Browse the repository at this point in the history
  • Loading branch information
texpert committed Feb 18, 2021
1 parent 45e674b commit 4af0245
Show file tree
Hide file tree
Showing 2 changed files with 28 additions and 0 deletions.
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,20 @@
# Changelog

## [v0.0.2](https://github.com/mejuri-inc/flowcommerce_spree/tree/v0.0.2) (2021-02-18)

[Full Changelog](https://github.com/mejuri-inc/flowcommerce_spree/compare/v0.0.1...v0.0.2)

**Merged pull requests:**

- \[TEC-4792\] Configuring price\_range to return min/max only [\#21](https://github.com/mejuri-inc/flowcommerce_spree/pull/21) ([sebastiandl](https://github.com/sebastiandl))

## [v0.0.1](https://github.com/mejuri-inc/flowcommerce_spree/tree/v0.0.1) (2021-02-03)

[Full Changelog](https://github.com/mejuri-inc/flowcommerce_spree/compare/b9071fa9cdf3afd5de85ff97de7141cdf5250419...v0.0.1)

**Merged pull requests:**

- \[NOTICKET\] Prepare the v0.0.1 release [\#15](https://github.com/mejuri-inc/flowcommerce_spree/pull/15) ([texpert](https://github.com/texpert))
- Fix the use of bundler by GitHub Actions and adding gemspec to the Gemfile [\#14](https://github.com/mejuri-inc/flowcommerce_spree/pull/14) ([texpert](https://github.com/texpert))
- \[TEC-4696\] GitHub check fix [\#11](https://github.com/mejuri-inc/flowcommerce_spree/pull/11) ([sebastiandl](https://github.com/sebastiandl))
- \[NO-TICKET\] configuring dotenvs to automatically load envs from env files [\#10](https://github.com/mejuri-inc/flowcommerce_spree/pull/10) ([sebastiandl](https://github.com/sebastiandl))
Expand Down
19 changes: 19 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,25 @@ Adapter for Spree, that allows using [Flow.io](https://www.flow.io) as payment g
## Gem Maintenance
### Preparing a release
Merge all the pull requests that should make it into the new release into the `main` branch, then checkout and pull the
branch and run the `github_changelog_generator`, specifying the new version as a `--future-release` cli parameter:
```
git checkout main
git pull

github_changelog_generator -u mejuri-inc -p flowcommerce_spree --future-release v0.0.2
```
Then push the `Preparing the new release` commit directly into the `main` branch:
```
git commit -m 'Preparing the new v0.0.2 release'
git push
```
### RubyGems credentials
Ensure you have the RubyGems credentials located in the `~/.gem/credentials` file.
Expand Down

0 comments on commit 4af0245

Please sign in to comment.