Closed sfeuga closed 3 years ago
@palkan beside question, where is the 0.4.0
version ?
Because, on this repo we only have the 0.3.2
version.
@sfeuga could you please fix the CI build? It seems we need to change just one line of code to fit the new Rubocop rules.
Regarding v0.4.0
- I believe it was not released because this version contains only one not important feature https://github.com/rubocop-hq/rubocop-md/commit/1a8004a55955d8304987de5638c3f5199fa76dfa#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edR5
@palkan For the v0.4.0
it's strange, it's available on rubygem.org.
~I'll fix the CI later today.~ Done.
For the v0.4.0 it's strange
I forgot to push the commit with the version.rb
change; my bad(
Thanks! Released in 0.4.1
When using rubocop 1.1.0 version,
running rubocop -r "rubocop-md"
raiseUnable to activate rubocop-md-0.3.2, because rubocop-1.1.0 conflicts with rubocop (~> 0.60)
error.According to the gem documentation I propose to update the version of rubocop in the
rubocop-md.gemspec
file.All rake test pass, tested on
Fedora 32
withruby --version ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux]
.