Skip to content

Conversation

@bastelfreak
Copy link
Contributor

backported from #82

smortex and others added 4 commits May 31, 2025 22:51
Only keep a single copy of the version string to avoid forgetting to
update it in one place when we bump it.
In the Vox Pupuli tradition, use labels in GitHub issues to generate a
human readable changelog when we release a new version of the code.
Some parts of CI run with a bundle without the packaging gems, we should
not raise an error if the github_changelog_generator gem is not found,
but rather tell how to fix that when the task is called.
config.project = "puppet"
config.exclude_labels = %w[dependencies duplicate question invalid wontfix wont-fix modulesync skip-changelog]
config.future_release = Puppet::PUPPETVERSION
config.since_tag = '7.36.1'
Copy link
Member

Choose a reason for hiding this comment

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

If we require_relative 'lib/puppet/version', we can:

Suggested change
config.since_tag = '7.36.1'
config.since_tag = Puppet::PUPPETVERSION

- Remove unused ContentsDescription class [\#44](https://github.com/OpenVoxProject/puppet/pull/44) ([ekohl](https://github.com/ekohl))
- Fix a typo and some formatting in the type and provider docs [\#43](https://github.com/OpenVoxProject/puppet/pull/43) ([smoeding](https://github.com/smoeding))
- Avoid closing directory we're iterating [\#42](https://github.com/OpenVoxProject/puppet/pull/42) ([ekohl](https://github.com/ekohl))
- Set version to 8.16.0 [\#40](https://github.com/OpenVoxProject/puppet/pull/40) ([nmburgan](https://github.com/nmburgan))
Copy link
Member

Choose a reason for hiding this comment

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

This should not appear in the 7.x changelog ;-)

@@ -1,6 +1,8 @@
require_relative 'lib/puppet/version'
Copy link
Member

Choose a reason for hiding this comment

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

This happened to be a terrible idea as the file is copied in AIO packages while it is used to generate the final .gemspec file when installing from a gem and the path do not match.

@smortex
Copy link
Member

smortex commented Jun 3, 2025

I succeeded in fixing the various issues I noted above in #93. Still not perfect due to bugs in GCG, but at least the information is consistent for PRs and does not inclue irrelevant issues. I will close this one in favor of it. Thank you!

@smortex smortex closed this Jun 3, 2025
nmburgan pushed a commit that referenced this pull request Sep 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants