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

chore(deps): update mszostok/codeowners-validator action to v0.7.4 #1208

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
mszostok/codeowners-validator action patch v0.7.1 -> v0.7.4

Release Notes

mszostok/codeowners-validator (mszostok/codeowners-validator)

v0.7.4

Compare Source

🎉 GitHub Codeowners Validator 0.7.4 is now available!

Highlights

✨ New functionality

First entry

 /build/logs/ @​octocat

Shadows - reported as error

 * @​s1
 /b*/logs @​s5

OK

 /b*/other @​o1
 /script/* @​o2
 ```

🔧 Bug Fixes

Changelog

v0.7.3

Compare Source

🎉 GitHub Codeowners Validator 0.7.3 is now available!

Highlights

✨ New functionality

  • not-owned-checker: Add git-ls-tree implementation with subdirectory support (#​141) (@​jeremycohen)
    Now you can specify against which subdirectories the not-owned check should be executed. To configure that, use the NOT_OWNED_CHECKER_SUBDIRECTORIES environment variable. In the default mode, it works as previously, where all files are checked.
  • Add GitHub token validation to get rid of misleading error checks (#​143)

🔧 Bug Fixes

  • Fix scope and internal error handling (#​145) (@​mszostok)
    The previous release informs the user about the internal error, but the exit code was not properly propagated. Now, besides the error message, the exit code is also set.

Changelog

v0.7.2

Compare Source

🎉 GitHub Codeowners Validator 0.7.2 is now available!

Highlights

🔧 Bug Fixes

✨ New checks

  • Add a flag to only allow teams as owners (#​127) (@​seveas)
    Now you can enable more strict rule and specify that only teams are allowed as owners of files.

🛡️ Security

Installation

See the Installation section for more installation options.

Docker images

ghcr.io:

  • docker pull ghcr.io/mszostok/codeowners-validator:stable
  • docker pull ghcr.io/mszostok/codeowners-validator:v0
  • docker pull ghcr.io/mszostok/codeowners-validator:v0.7
  • docker pull ghcr.io/mszostok/codeowners-validator:v0.7.2
Changelog 🚀

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested review from a team as code owners March 3, 2024 10:42
@renovate renovate bot requested review from kevcube and nitrocode and removed request for a team March 3, 2024 10:42
@cloudpossebot
Copy link
Member

Important

No Changes Were Applied

This Pull Request was merged without using the auto-apply label; therefore, no changes were applied upon merging.

Review the associated issues and, if applicable, tag each with the apply label to apply the changes.

Copy link
Contributor Author

renovate bot commented Mar 3, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v0.7.4). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/mszostok-codeowners-validator-0.x branch March 3, 2024 11:28
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.

2 participants