Jira (PUP-11844) puppet 8.0.0 gem has an incorrect required ruby version
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11844 puppet 8.0.0 gem has an incorrect required ruby version Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Puppet 8.0.0 did not specify the correct minimum ruby version, so it was possible to install it on Ruby 2.7 or 3.0, and then fail to run. Now the puppet gem metadata correctly requires ruby 3.1 or greater. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484831.1682523824000.8940.1682534160029%40Atlassian.JIRA.
Jira (PUP-11844) puppet 8.0.0 gem has an incorrect required ruby version
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-11844 puppet 8.0.0 gem has an incorrect required ruby version Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484831.1682523824000.8852.1682532300104%40Atlassian.JIRA.
Jira (PUP-11844) puppet 8.0.0 gem has an incorrect required ruby version
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11844 puppet 8.0.0 gem has an incorrect required ruby version Change By: Josh Cooper Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484831.1682523824000.8851.1682532300040%40Atlassian.JIRA.
Jira (PUP-11844) puppet 8.0.0 gem has an incorrect required ruby version
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11844 puppet 8.0.0 gem has an incorrect required ruby version Change By: Josh Cooper Sprint: Phoenix 2023-05-10 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484831.1682523824000.8853.1682532300151%40Atlassian.JIRA.
Jira (PUP-11844) puppet 8.0.0 gem has an incorrect required ruby version
Title: Message Title Josh Cooper created an issue Puppet / PUP-11844 puppet 8.0.0 gem has an incorrect required ruby version Issue Type: Bug Affects Versions: PUP 8.0.0 Assignee: Unassigned Created: 2023/04/26 8:43 AM Fix Versions: PUP 8.0.1 Priority: Normal Reporter: Josh Cooper The puppet 8.0.0 gem on rubygems. org lists the minimum required version as >= 2.7, but will fail to run if the actual ruby version is < 3.1. So module CI using Ruby 2.7 or 3.0 with unconstrained puppet versions will pull in the puppet 8 gem and fail. I'm going to file a pdk lint check for unconstrained puppet versions, but that being said, the puppet gem versioning should be consistent. This issue was caused because we have two sources of truths for gem metadata. We bumped .gemspec, but not ext/project_data.yaml. The latter is what is actually used when building & shipping gems. There are two sources of truth, because circa 8+ years ago, ruby and bundler didn't handle platform specific gems well. So we added the gem dependencies to project_data.yaml. We added this note to the .gemspec and project_data.yaml to try to avoid this, but didn't take our own advice. See also PA-1077
