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 5.0.0.rc1 [ci skip]

This commit is contained in:
Daniel Colson 2019-01-05 22:54:07 -05:00
parent ab8ed30424
commit 75806f33ad
No known key found for this signature in database
GPG key ID: 88A364BBE77B1353
4 changed files with 14 additions and 5 deletions

View file

@ -1,7 +1,7 @@
PATH PATH
remote: . remote: .
specs: specs:
factory_bot_rails (4.11.1) factory_bot_rails (5.0.0.rc1)
factory_bot (~> 5.0.0.rc1) factory_bot (~> 5.0.0.rc1)
railties (>= 4.2.0) railties (>= 4.2.0)

8
NEWS
View file

@ -1,6 +1,14 @@
factory_bot_rails versioning is synced with factory_bot releases. For this reason 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. there might not be any notable changes in new versions of this project.
5.0.0
Added: calling reload! in the Rails console will reload any factory definition files that have changed
Added: support for custom generator templates
Added: definition_file_paths configuration option, making it easier to place factories in custom locations
Changed: namespaced models are now generated inside a directory matching the namespace
Changed: added newline between factories generated into the same file
Removed: support for EOL version of Ruby and Rails
4.11.1 (September 7, 2018) 4.11.1 (September 7, 2018)
Update generator to use dynamic attributes instead of deprecated static attributes Update generator to use dynamic attributes instead of deprecated static attributes

View file

@ -1,14 +1,15 @@
# Releasing # Releasing
1. Update the version in the gemspec (and the factory_bot version, if necessary) 1. Update the version in the gemspec (and the factory\_bot version, if necessary)
and run `bundle install`
1. Update `NEWS.md` to reflect the changes since last release. 1. Update `NEWS.md` to reflect the changes since last release.
1. Commit changes. 1. Commit changes.
There shouldn't be code changes, There shouldn't be code changes,
and thus CI doesn't need to run, and thus CI doesn't need to run,
you can then add "[ci skip]" to the commit message. so you can add "[ci skip]" to the commit message.
1. Tag the release: `git tag -s vVERSION` 1. Tag the release: `git tag -s vVERSION`
- We recommend the [_quick guide on how to sign a release_] from git ready. - We recommend the [_quick guide on how to sign a release_] from git ready.
1. Push changes: `git push --tags` 1. Push changes: `git push && git push --tags`
1. Build and publish: 1. Build and publish:
```bash ```bash
gem build factory_bot_rails.gemspec gem build factory_bot_rails.gemspec

View file

@ -1,6 +1,6 @@
Gem::Specification.new do |s| Gem::Specification.new do |s|
s.name = "factory_bot_rails" s.name = "factory_bot_rails"
s.version = "4.11.1" s.version = "5.0.0.rc1"
s.authors = ["Joe Ferris"] s.authors = ["Joe Ferris"]
s.email = "jferris@thoughtbot.com" s.email = "jferris@thoughtbot.com"
s.homepage = "https://github.com/thoughtbot/factory_bot_rails" s.homepage = "https://github.com/thoughtbot/factory_bot_rails"