Release 3.1.0 #347
Merged
Release 3.1.0 #347
Conversation
This file contains 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
jhoblitt
reviewed
Mar 1, 2023
CHANGELOG.md
Outdated
|
|
||
| **Closed issues:** | ||
|
|
||
| - Stop managing alias map \(/etc/aliases\) [\#337](https://github.com/voxpupuli/puppet-postfix/issues/337) |
There was a problem hiding this comment.
Are these bugs or enhancements?
There was a problem hiding this comment.
I guess this should have been tagged skip-changelog… Updating…
|
I believe that modulesync + release in a single PR isn't something that has been commonly done in voxpupuli. I am in favor of this as it reduces the overhead in shipping a release. |
bastelfreak
approved these changes
Mar 1, 2023
bastelfreak
approved these changes
Mar 1, 2023
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.
As noted in #346, the documentation of the latest version of the module on the forge is a bit misleading and quite a number of fixes have been integrated since the last release in May last year.
We also have #256 which introduce a breaking change, so I propose to do a release without it for now, and merge that PR when it is done.
This PR also include: