Skip to content

Commit

Permalink
Update changelog, clarify that 0.11 has been released
Browse files Browse the repository at this point in the history
  • Loading branch information
@jaredbeck
jaredbeck committed Mar 31, 2016
1 parent 34cd8a3 commit 06fad20
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
@@ -1,8 +1,12 @@
# Carrierwave History/Changelog

All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/).

## [Unreleased]
## 0.11.0 - 2016-03-29

[Compare v0.10.0...v0.11.0](https://github.com/carrierwaveuploader/carrierwave/compare/v0.10.0...v0.11.0)

### Added
* Add a test matcher for the format (@yanivpr [#1758](https://github.com/carrierwaveuploader/carrierwave/pull/1758))
* Support of MiniMagick's Combine options (@bernabas [#1754](https://github.com/carrierwaveuploader/carrierwave/pull/1754))
Expand Down Expand Up @@ -61,7 +65,8 @@ This project adheres to [Semantic Versioning](http://semver.org/).
* Make the `#remove_#{column}` accessor set the mounted column as changed (@nikz [#1326](https://github.com/carrierwaveuploader/carrierwave/pull/1326))
* Tempfile and @content_type assignment (@bensie [#1487](https://github.com/carrierwaveuploader/carrierwave/issues/1487))

## 0.10.0 - 2014-02-26

Please check [0.10-stable] for previous changes.

[Unreleased]: https://github.com/carrierwaveuploader/carrierwave/compare/v0.10.0...HEAD
[0.10-stable]: https://github.com/carrierwaveuploader/carrierwave/blob/0.10-stable/History.txt

3 comments on commit 06fad20

@mattmenefee
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jaredbeck / maintainers: it looks like the releases page was previously being used to document changes. Could someone copy the changes listed in the CHANGELOG.md to the releases page for the latest release for the purpose of consistency?

@mattmenefee
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the changes related to #1819 were not actually included in the v0.11.0 tagged release.

@jaredbeck
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could someone copy the changes listed in the CHANGELOG.md to the releases page ..

I prefer using a plaintext file like CHANGELOG.md to avoid vendor lock-in, but if you must use github releases, please delete CHANGELOG.md. Thanks.

Please # to comment.