[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)
Welcome to [Renovate](https://togithub.com/renovatebot/renovate)! This
is an onboarding PR to help you understand and configure settings before
regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate,
simply close this Pull Request unmerged.
---
### Detected Package Files
* `Dockerfile` (dockerfile)
* `Dockerfile.test` (dockerfile)
### Configuration Summary
Based on the default config's presets, Renovate will:
- Start dependency updates only once this onboarding PR is merged
- Show all Merge Confidence badges for pull requests.
- Enable Renovate Dependency Dashboard creation.
- Use semantic commit type `fix` for dependencies and `chore` for all
others if semantic commits are in use.
- Ignore `node_modules`, `bower_components`, `vendor` and various
test/tests directories.
- Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
- Run lock file maintenance (updates) early Monday mornings.
- Schedule automerge daily.
- Schedule for weekends.
- Run Renovate on following schedule: every weekend
🔡 Do you want to change how Renovate upgrades your dependencies? Add
your custom config to `renovate.json` in this branch. Renovate will
update the Pull Request description the next time it runs.
---
### What to Expect
With your current configuration, Renovate will create 1 Pull Request:
<details>
<summary>chore(deps): update alpine docker tag to v3.19</summary>
- Schedule: ["every weekend"]
- Branch name: `renovate/alpine-3.x`
- Merge into: `main`
- Upgrade alpine to `3.19`
</details>
---
❓ Got questions? Check out Renovate's
[Docs](https://docs.renovatebot.com/), particularly the Getting Started
section.
If you need any further assistance then you can also [request help
here](https://togithub.com/renovatebot/renovate/discussions).
---
This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/woodpecker-ci/plugin-kaniko).
<!--renovate-config-hash:160fba6c1384e49cc565c5a1ec2b1afdfd96eb8be069aa9e94322d8ff975ea8f-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Apparently the busybox implementation of `base64` will line-wrap long output strings.
This meant that long username+password combinations could produce base64 that
contained spurious "\n" characters, which then led to:
```
2019/05/06 00:47:39 Unable to parse "/kaniko/.docker/config.json": invalid character '\n' in string literal
```
Fixed by just removing the newlines in base64 output. A "better" solution would use a different base64
implementation that avoided line-wrapping in the first place.