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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency pihole/pihole to v2022.04.3 (old) #136

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency pihole/pihole to v2022.04.3 (old) #136

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2022 •
edited
Loading

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
pihole/pihole final patch 2022.04.2 -> 2022.04.3

Release Notes

pi-hole/docker-pi-hole

v2022.04.3

Compare Source

Docker specific changes

New Contributors

Full Changelog: pi-hole/docker-pi-hole@2022.04.2...2022.04.3

This release also contains updates for the 3 main components (FTL v5.15, Web v5.12, and Core v5.10), Changelogs below:

What's Changed (FTL 5.15)

New Contributors

Full Changelog: pi-hole/FTL@v5.14...v5.15

What's Changed (Web 5.12)

New Contributors

Full Changelog: pi-hole/web@v5.11...v5.12

What's Changed (Core 5.10)

New Contributors

Full Changelog: pi-hole/pi-hole@v5.9.1...v5.10

Configuration

📅 Schedule: 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, click this checkbox.

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

@klutchell
Copy link
Owner

klutchell commented Apr 22, 2022 •
edited
Loading

@eiddor I've enabled renovate on this repo to open PRs for us to speed up testing.

However, renovate will not update balena.yml for us. So we can add commits to these branches manually, or open our own PR in parallel after we've done some testing.

I expect this automation will help a little bit, but not a lot as there are still some manual commits required.

What do you think?

Also, renovate PRs have access to GH secrets so it can push to my fleet and I can start testing even without the balena.yml changes.

@klutchell klutchell mentioned this pull request Apr 22, 2022
Closed
@eiddor
Copy link
Collaborator

eiddor commented Apr 22, 2022

renovatebot.com seems to be down (or internal), so I'm not entirely sure what it is - Does it just monitor a parent repo/container and automatically open a PR? I'll dig into the workflow stuff to try to learn it.

Seems like it would help to at least light a fire under us to keep things up to date, plus it sounds kind of cool.

@klutchell
Copy link
Owner

klutchell commented Apr 25, 2022 •
edited
Loading

@eiddor the link is back up now: https://www.whitesourcesoftware.com/free-developer-tools/renovate/

I'm still a bit torn on this. I'm going to see if I can add a custom step to renovate to bump balena.yml otherwise we will end up with draft releases that do not reflect the new semver. Not a huge deal if we can start testing the release sooner, but if we are going to replace manual steps with automation it should at least be feature complete.

@klutchell
Copy link
Owner

I'm going to give this configuration a try and use this PR to test the result.
https://docs.renovatebot.com/configuration-options/#postupgradetasks

@renovate renovate bot force-pushed the renovate/pihole-pihole-2022.x branch from 3fd1609 to cd1b53d Compare April 25, 2022 23:24
@renovate
Copy link
Contributor Author

renovate bot commented Apr 25, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pihole/Dockerfile
Post-upgrade command './postUpgrade.sh {{{depName}}} {{{newVersion}}}' does not match allowed pattern '^pwd$'

@klutchell klutchell closed this Apr 26, 2022
@klutchell klutchell changed the title chore(deps): update dependency pihole/pihole to v2022.04.3 chore(deps): update dependency pihole/pihole to v2022.04.3 (old) Apr 26, 2022
@klutchell klutchell deleted the renovate/pihole-pihole-2022.x branch April 26, 2022 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@klutchell @eiddor @renovate-bot