Closed javierbertoli closed 2 years ago
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
As described in
repositories entries in the Debian's family are being re-added each time the formula is run.
As proposed here, moved away from pkgrepo and manage the repository's file with file.managed.
pkgrepo
file.managed
Used the same parameters to keep it backward compatible.
README
Available states
pillar.example
state_top
:tada: This PR is included in version 2.4.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
As described in
repositories entries in the Debian's family are being re-added each time the formula is run.
Describe the changes you're proposing
As proposed here, moved away from
pkgrepo
and manage the repository's file withfile.managed
.Used the same parameters to keep it backward compatible.
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context