Skip to content

Commit

Permalink
Bump to version 5.0.1
Browse files Browse the repository at this point in the history
  • Loading branch information
andreamazz committed Apr 20, 2018
1 parent 24e3bc6 commit 1ed6db3
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 3 deletions.
2 changes: 1 addition & 1 deletion AMScrollingNavbar.podspec
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Pod::Spec.new do |s|
s.name = "AMScrollingNavbar"
s.version = "5.0.0"
s.version = "5.0.1"
s.summary = "A custom UINavigationController that enables the scrolling of the navigation bar alongside the scrolling of an observed content view"
s.description = <<-DESC
A custom UINavigationController that enables the scrolling of the
Expand Down
8 changes: 6 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
All notable changes to this project will be documented in this file.
`AMScrollingNavbar` adheres to [Semantic Versioning](http://semver.org/).

- `5.0.x` Releases - [5.0.0](#500)
- `5.0.x` Releases - [5.0.0](#500) | [5.0.1](#501)
- `4.3.x` Releases - [4.3.0](#430) | [4.3.1](#431)
- `4.2.x` Releases - [4.2.0](#420) | [4.2.1](#421) | [4.2.2](#422) | [4.2.3](#423) | [4.2.4](#424)
- `4.1.x` Releases - [4.1.0](#410)
Expand All @@ -21,9 +21,13 @@ All notable changes to this project will be documented in this file.

## [5.0.0](https://github.com/andreamazz/AMScrollingNavbar/releases/tag/5.0.0)

- Fixed #313

## [5.0.0](https://github.com/andreamazz/AMScrollingNavbar/releases/tag/5.0.0)

### Breaking changes

The followers are no longer plain `UIView`s, but need to be wrapped in a `NavigationBarFollower` object, that provides the direction of the scroll.
The followers are no longer plain `UIView`s, but need to be wrapped in a `NavigationBarFollower` object, that provides the direction of the scroll.

## [4.3.1](https://github.com/andreamazz/AMScrollingNavbar/releases/tag/4.3.1)

Expand Down

0 comments on commit 1ed6db3

Please sign in to comment.