-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release a new version of the gem??? #117
Comments
@spovich I did fork the gem and apply all the pull requests here: Released it as a gem: ipaddress_2 |
@Adam21e great, thank you! Giving it a look now. |
jivdhaliwal
pushed a commit
to ministryofjustice/staff-device-dns-dhcp-admin
that referenced
this issue
Aug 24, 2020
The ipaddress_2 gem includes fixes that have been sitting in the master branch of ipaddress_2 for years without a gem release. Specifically the issue of valid? not validating ipv4 subnets correctly (ipaddress-gem/ipaddress#110) In the ipaddress gem you get the following IPAddress::valid? "10.0.0.0/24" => false But in ipaddress_2 this has been resolved and you get IPAddress::valid? "10.0.0.0/24" => true ipaddress-gem/ipaddress#117
jivdhaliwal
pushed a commit
to ministryofjustice/staff-device-dns-dhcp-admin
that referenced
this issue
Aug 24, 2020
The ipaddress_2 gem includes fixes that have been sitting in the master branch of ipaddress_2 for years without a gem release. Specifically the issue of valid? not validating ipv4 subnets correctly (ipaddress-gem/ipaddress#110) In the ipaddress gem you get the following IPAddress::valid? "10.0.0.0/24" => false But in ipaddress_2 this has been resolved and you get IPAddress::valid? "10.0.0.0/24" => true ipaddress-gem/ipaddress#117
Closed
Tracking this here: #132 Closing this issue, as I'm going through and cleaning up some outstanding issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The last release was 4 years ago. The project seems to be actively maintained, so just wondering if there is a reason for no release?
The text was updated successfully, but these errors were encountered: