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

Fix extra newline at end of headers #2514

Merged
merged 1 commit into from Jan 2, 2024
Merged

Conversation

smortex
Copy link
Collaborator

@smortex smortex commented Jan 2, 2024

This slept through while converting templates form erb to epp. Remove
it so that it is easier to spot regressions if the catalog is not
supposed to change but applying it in noop mode wants to change the
actual files.

This slept through while converting templates form erb to epp.  Remove
it so that it is easier to spot regressions if the catalog is not
supposed to change but applying it in noop mode wants to change the
actual files.
@smortex smortex added the bugfix label Jan 2, 2024
@smortex smortex marked this pull request as ready for review January 2, 2024 16:57
@smortex smortex requested review from bastelfreak, ekohl and a team as code owners January 2, 2024 16:57
@smortex
Copy link
Collaborator Author

smortex commented Jan 2, 2024

This issue was reported by @vchepkov on slack, I would like to see it released in a 12.0.1 version before we merge backward-incompatble change if you don't mind @ekohl?

@vchepkov
Copy link

vchepkov commented Jan 2, 2024

I concur, this fixes it for me

@ekohl ekohl merged commit 7de9755 into main Jan 2, 2024
45 checks passed
@ekohl ekohl deleted the fix-extra-newline-at-end-of-headers branch January 2, 2024 18:16
@ekohl
Copy link
Collaborator

ekohl commented Jan 2, 2024

This issue was reported by @vchepkov on slack, I would like to see it released in a 12.0.1 version before we merge backward-incompatble change if you don't mind @ekohl?

I'm wondering if it's wise to do a major release so soon after. On the other hand, people can bump 2 releases at once

@smortex
Copy link
Collaborator Author

smortex commented Jan 2, 2024

@ekohl I personally do not really care about how ofter major release happen… they happen when they happen 🤷

We can also have breaking changes labelled as such that wait not merged, and when we feel a new major release make sense merge them. I think it is something we try to do with some voxpupuli modules (e.g. merge a PR that deprecate something and open a PR that remove the deprecation that is ready to merge).

Do you think we should trigger a 12.0.1 with this fix, or do we merge these backward-incompatible PRs and go far a 13.0.0?

@ekohl
Copy link
Collaborator

ekohl commented Jan 3, 2024

12.0.1 now sounds good. Major versions are a pain in reverse dependencies because they require a release. In the Foreman context it means I need to do that in 3 modules. 3 commits to bump and 3 module releases

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.

None yet

5 participants