Skip to content
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

(CAT-1301) Pin changelog generator gem #143

Merged
merged 1 commit into from
Aug 21, 2023
Merged

Conversation

GSPatton
Copy link

Prior to this commit, a bundle install on some systems failed due to Gemfile conflicts arising from the changelog generator gem. This commit pins it to v1.15.0

Summary

Provide a detailed description of all the changes present in this pull request.

Additional Context

Add any additional context about the problem here.

  • Root cause and the steps to reproduce. (If applicable)
  • Thought process behind the implementation.

Related Issues (if any)

Mention any related issues or pull requests.

Checklist

  • 🟢 Spec tests.
  • 🟢 Acceptance tests.
  • Manually verified.

Prior to this commit, a bundle install on some systems failed due to Gemfile conflicts arising from the changelog generator gem. This commit pins it to v1.15.0
@david22swan david22swan merged commit e01caaa into main Aug 21, 2023
7 checks passed
@david22swan david22swan deleted the CAT-1301-Pin_changelog_gen branch August 21, 2023 09:38
@@ -22,7 +22,7 @@ group :acceptance do
end

group :development do
gem 'github_changelog_generator', require: false
gem 'github_changelog_generator', '~> 1.15.0', require: false
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @david22swan , we (vox pupuli) had some problems with older versions of the gem, so we pinned to ~> 1.16.4. This was some time ago so I cannot remember the actual issues we faced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants