Repository navigation
(fix) Module release prep workflow to include ruby version input and configure forge authentication - #189
Merged
Conversation
…configure forge authentication
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Module release prep was missing Forge authentication which is required when the minimum version being released is Puppet 8.
Duplicated the configuration used by module CI, including moving the Ruby version as an input variable where further Ruby configuration is required.
Additional Context
Modules such as puppetlabs-hocon and puppetlabs-puppet_authorization will fail during module release prep at the bundler step due to missing Forge credentials where Puppet 8 is the minimum supported version.