1
0
Fork 0
mirror of https://github.com/thoughtbot/factory_bot_rails.git synced 2022-11-09 11:49:18 -05:00

Bump version to 4.11.0 [ci skip]

This commit is contained in:
Daniel Colson 2018-08-16 07:27:22 -04:00
parent c4f561d2d7
commit 9f4323f415
3 changed files with 29 additions and 2 deletions

3
NEWS
View file

@ -1,6 +1,9 @@
factory_bot_rails versioning is synced with factory_bot releases. For this reason
there might not be any notable changes in new versions of this project.
4.11.0 (August 16, 2018)
No notable changes
4.10.0 (May 25, 2018)
No notable changes

24
RELEASING.md Normal file
View file

@ -0,0 +1,24 @@
# Releasing
1. Update the version in the gemspec (and the factory_bot version, if necessary)
1. Update `NEWS.md` to reflect the changes since last release.
1. Commit changes.
There shouldn't be code changes,
and thus CI doesn't need to run,
you can then add "[ci skip]" to the commit message.
1. Tag the release: `git tag -s vVERSION`
- We recommend the [_quick guide on how to sign a release_] from git ready.
1. Push changes: `git push --tags`
1. Build and publish:
```bash
gem build factory_bot_rails.gemspec
gem push factory_bot_rails-VERSION.gem
```
1. Add a new GitHub release using the recent `NEWS.md` as the content. Sample
URL: https://github.com/thoughtbot/factory_bot_rails/releases/new?tag=vVERSION
1. Announce the new release,
making sure to say "thank you" to the contributors
who helped shape this version!
[_quick guide on how to sign a release_]: http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html

View file

@ -1,6 +1,6 @@
Gem::Specification.new do |s|
s.name = %q{factory_bot_rails}
s.version = '4.10.0'
s.version = '4.11.0'
s.authors = ["Joe Ferris"]
s.email = %q{jferris@thoughtbot.com}
s.homepage = "https://github.com/thoughtbot/factory_bot_rails"
@ -16,5 +16,5 @@ Gem::Specification.new do |s|
s.license = "MIT"
s.add_runtime_dependency('railties', '>= 3.0.0')
s.add_runtime_dependency('factory_bot', '~> 4.10.0')
s.add_runtime_dependency('factory_bot', '~> 4.11.0')
end