Closed dmke closed 7 months ago
It looks like v5.0.0 didn't make it to RubyGems as well. :thinking:
@dmke Thanks for the report.
Now, I am currently busy with "No Auth, No Entry" related tasks, so I will release v4.25.16p1
(or p2
?) to RubyGems next week.
If you need v4.25.16p1 before it is released to RubyGems, you can get it via git clone -b 4-stable https://github.com/sisimai/rb-sisimai.git
.
It looks like v5.0.0 didn't make it to RubyGems as well. 🤔
We are currently working on the README.md and documentation in libsisimai.org for Sisimai 5, and we plan to release v5.0.0
to RubyGems once they are completed. This is expected to take a few weeks.
Best regards,
Thank you for the information.
I've already upgraded to v5.0.0 using the git_source
method mentioned above. I'm not actually waiting for a full release, so take your time :)
The README for the Perl version of Sisimai 5 is available at https://github.com/sisimai/p5-sisimai/pull/500/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5, although it has not been merged yet. The functionality is compatible with the Ruby version, so please refer to it if you find it helpful. :-)
Yesterday, after the release of 4.25.16p1, I wanted to update sisimai-web accordingly, but was surprised that RubyGems doesn't list that version:
In general, this is not much of a problem, because I can just change the Gemfile entry (cf. a934ad0a):
However, today I got a PR from dependabot, which seems to interpret the
p1
suffix as some kind of pre-release (Semver defines MAJOR "." MINOR "." PATCH ["-" prerelease] ["+" build]), and dutifully "upgrades" to 4.25.16...So, long story short: Would you mind releasing 4.25.16p1 as 4.25.16.1 to RubyGems?