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

docs: Add trustLevel info to allowedPostUpgradeCommands #8597

Merged
merged 2 commits into from
Feb 9, 2021

Conversation

aizerin
Copy link
Contributor

@aizerin aizerin commented Feb 8, 2021

Changes:

Added info about trustLevel into allowedPostUpgradeCommands section.

Context:

I was not able to figure out why allowedPostUpgradeCommands does not work and I found in source code that trustLevel must be set to high. So this information may help other lost people :)

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added unit tests, or
  • No new tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
@rarkins rarkins changed the title Add trustLevel info to allowedPostUpgradeCommands docs: Add trustLevel info to allowedPostUpgradeCommands Feb 9, 2021
@HonkingGoose

This comment has been minimized.

@HonkingGoose
Copy link
Collaborator

I've made 2 PRs that aim to resolve my review comments, they are linked above this comment.

@rarkins rarkins merged commit b079caf into renovatebot:master Feb 9, 2021
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 24.43.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants