Skip to content

Commit

Permalink
Bump version to 2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@jkowens
jkowens committed Jul 18, 2022
1 parent 01e907f commit 21a0b3e
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
3 changes: 3 additions & 0 deletions README.md
View file
Expand Up @@ -176,6 +176,9 @@ Mustermann follows [Semantic Versioning 2.0](http://semver.org/). Anything docum

### Stable Releases

* **Mustermann 2.0.0** (2022-07-18)
* Improve Ruby 3 compatibility. Removed built-in Sinatra 1 support, and moved to new mustermann-sinatra-extension gem. Fixes [#114](https://github.com/sinatra/mustermann/issues/114) [@epergo](https://github.com/epergo)

* **Mustermann 1.1.2** (2022-07-16)
* Add compatibility with --enable=frozen-string-literal param. Fixes [#110](https://github.com/sinatra/mustermann/issues/110) [@michal-granec](https://github.com/michal-granec)

Expand Down
2 changes: 1 addition & 1 deletion mustermann/lib/mustermann/version.rb
View file
@@ -1,4 +1,4 @@
# frozen_string_literal: true
module Mustermann
VERSION ||= '1.1.2'
VERSION ||= '2.0.0'
end

6 comments on commit 21a0b3e

@dentarg
Copy link
Member

Choose a reason for hiding this comment

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

Missed opportunity to drop support for EoL Rubies?

mustermann/mustermann/mustermann.gemspec

Line 13 in 21a0b3e

s.required_ruby_version = '>= 2.2.0'

@jkowens
Copy link
Member Author

@jkowens jkowens commented on 21a0b3e Jul 19, 2022 via email

Choose a reason for hiding this comment

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

@dentarg
Copy link
Member

Choose a reason for hiding this comment

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

Mustermann 3.0 would fit nicely with Sinatra 3.0 though? :)

@jkowens
Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, I think we could do that 😄 I should probably release a 2.0.1 with the proper fix for the ruby2_keywords issue. Then we could release 3.0 with the dropped Rubies support. Would >= 2.6 be what we what to go to?

@dentarg
Copy link
Member

Choose a reason for hiding this comment

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

I think so! That matches Sinatra: sinatra/sinatra#1699 (sinatra/sinatra@9a924aa)

@jkowens
Copy link
Member Author

Choose a reason for hiding this comment

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

#133

Please sign in to comment.