profile
viewpoint
Simon Elsbrock elsbrock ᕕ( ᐛ )ᕗ Germany Software Engineer

ChristianBoehlke/circleci-recent-builds 6

Show CircleCI recent builds in your command line

elsbrock/Dancer-Plugin-Auth-Twitter 1

authenticate users with Twitter OAuth

elsbrock/edgerouter-backup 1

Backing up the configuration of Ubiquiti's Edgerouter to a Github repository

elsbrock/ansible 0

Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications— automate in a language that approaches plain English, using SSH, with no agents to install on remote systems.

elsbrock/ansible-modules-core 0

Ansible modules - these modules ship with ansible

elsbrock/bootimg-tools 0

Android boot.img creation and extraction tools (also MinGW compatible)

elsbrock/cobra 0

A Commander for modern Go CLI interactions

elsbrock/community 0

Kubernetes community content

elsbrock/coredns-ipecho 0

ipecho is an coredns plugin, it answers ip subdomain queries with the ip itself.

startedwillmcgugan/rich

started time in a day

startedohler55/ojg

started time in a day

startedGoogleCloudPlatform/k8s-config-connector

started time in 7 days

startedcontainernetworking/cni

started time in 7 days

issue openedcaddyserver/caddy

Access log is logging `Authorization` headers

Hi,

given this config snippet:

    :8080 {
      log {
        format console
      }
      reverse_proxy https://example.com:443 {
        header_up Host example.com
      }
    }

I noticed that by default Caddy seems to log Authorization headers:

 prometheus-proxy 1.5934604916540647e+09    info    http.log.access.log0    handled request    {"request": {"method": "GET", "uri": "/foobar", "proto": "HTTP/1.1", "remote_addr": "redacted", "host": "10.16
 .0.219:8080", "headers": {"User-Agent": ["Prometheus/2.12.0"], "Accept": ["application/openmetrics-text; version=0.0.1,text/plain
 ;version=0.0.4;q=0.5,*/*;q=0.1"], "Accept-Encoding": ["gzip"], "Authorization": ["Basic $SHOULD_NOT_BE_WRITTEN_TO_LOG"]}}, "common_log": "10.16.1.11 - -
  [29/Jun/2020:19:54:51 +0000] \"GET /foobar HTTP/1.1\" 200 21520", "duration": 0.138742971, "size": 21520, "status": 200, "resp_headers": {"Content-Encoding": ["gzip"], "Server": ["Caddy", "cloudflare"], "Strict
 -Transport-Security": ["max-age=31536000; includeSubDomains; preload"], "Date": ["Mon, 29 Jun 2020 19:54:51 GMT"], "Content-Type": ["text/plain; version=0.0.4; charset=utf-8"]}}

Note the "Authorization": ["Basic $SHOULD_NOT_BE_WRITTEN_TO_LOG"]. Is that intended? If so, how do I turn it off? And: shouldn't that rather be a safe default?

Thanks!

created time in 7 days

startedmaxgoedjen/secretive

started time in 8 days

startedccrama/Slide

started time in 8 days

startedpirate/ArchiveBox

started time in 8 days

starteddosyago/22120

started time in 8 days

startedkelda/blimp

started time in 9 days

startedOctoPrint/OctoPrint

started time in 9 days

startedgokrazy/stat

started time in 9 days

startedTomHarte/CLK

started time in 10 days

startedpoundifdef/plainoldrecipe

started time in 10 days

startedchubin/wttr.in

started time in 10 days

startedgitalk/gitalk

started time in 12 days

issue commentcoreos/prometheus-operator

Scrape external service with FQDN

Right, but in our case the Prometheus instance is running in an entirely different network segment, so we either need to use the global config (which I don't find to be nice from dependency point of view, a ServiceMonitor seems much better) or set up a reverse proxy pod that I can then scrape using a ServiceMonitor.

shay-berman

comment created time in 12 days

startedklauspost/compress

started time in 13 days

startedmh-/diagnosis-keys

started time in 13 days

startedSwordfish90/cool-retro-term

started time in 13 days

startedsvenstaro/proxyboi

started time in 14 days

startediamadamdev/bypass-paywalls-chrome

started time in 15 days

startedvividvilla/ezhil

started time in 15 days

issue commentcoreos/prometheus-operator

Scrape external service with FQDN

You cannot in a meaningful way monitor external services as prometheus needs to scrape each instance/process individually. That’s why you need to use a separate discovery mechanism that actually does discover all processes.

One use case I see is federation, where I want to configure another Prometheus instance as target to be scraped. It'd be great if that were possible by means of a ServiceMonitor.

shay-berman

comment created time in 15 days

startedossu/computer-science

started time in 15 days

startedrauc/rauc

started time in 15 days

issue commentrancher/docs

rancherOS in the docs - comment on EOL coming soon

Too bad I only found out now. I agree this should be made more transparent.

vrms

comment created time in 16 days

startedjbub/ghostwriter

started time in 16 days

startedTRON-US/go-btfs

started time in 17 days

startedjohang/btfs

started time in 17 days

push eventelsbrock/edgerouter-backup

Simon Elsbrock

commit sha 54ad856fb8238d99eafe52945c2362293cae0bd8

Set theme jekyll-theme-cayman

view details

push time in 17 days

startedmarq24/UUID0xFD6FTracer

started time in 17 days

issue closedflatcar-linux/docs

How to update the config of an existing Flatcar instance?

Current situation I am interested in giving Flatcar a try but was unable to find an answer to the following question: Assuming I have successfully installed a Flatcar instance and would like to update its config, how do I do this? I understand I would have to use ct to transform it into an ignition.json, but how do I actually apply it? The way I understand it is that it depends on the environment, but I am unable to find specifics.

Ideal future situation There is a section that explains how to update the configuration of a given instance.

Additional information I am new to Flatcar, so I might just have missed the obvious 😄

closed time in 18 days

elsbrock

startedrancher/k3os

started time in 18 days

startedgithub/super-linter

started time in 18 days

startedsimonfrey/s4

started time in 19 days

startedmikeslattery/tunic

started time in 22 days

startedventoy/Ventoy

started time in 22 days

startednotnil/chess

started time in 22 days

startedvlang/v

started time in 22 days

startedAssemblyScript/assemblyscript

started time in 23 days

startedgcc-mirror/gcc

started time in 23 days

startedakamai/openssl

started time in 23 days

startedweg-li/weg-li

started time in 23 days

issue openedflatcar-linux/docs

How to update the config of an existing Flatcar instance?

Current situation I am interested in giving Flatcar a try but was unable to find an answer to the following question: Assuming I have successfully installed a Flatcar instance and would like to update its config, how do I do this? I understand I would have to use ct to transform it into an ignition.json, but how do I actually apply it? The way I understand it is that it depends on the environment, but I am unable to find specifics.

Ideal future situation There is a section that explains how to update the configuration of a given instance.

Additional information I am new to Flatcar, so I might just have missed the obvious 😄

created time in 23 days

startedgeerlingguy/turing-pi-cluster

started time in 23 days

startedcarlosedp/cluster-monitoring

started time in 23 days

delete branch elsbrock/tilejson-dl

delete branch : renovate/canvas-1.x

delete time in 23 days

push eventelsbrock/tilejson-dl

Renovate Bot

commit sha 04e9c0bcc1691986732e6cd908cec8a44763fc8f

Update dependency canvas to v1.6.13

view details

Simon Elsbrock

commit sha 42b57d2b3da53d0a5ca3632b43a9c7520373257f

Merge pull request #5 from elsbrock/renovate/canvas-1.x Update dependency canvas to v1.6.13

view details

push time in 23 days

PR merged elsbrock/tilejson-dl

Update dependency canvas to v1.6.13

This PR contains the following updates:

Package Type Update Change
canvas dependencies patch 1.6.10 -> 1.6.13

Release Notes

<details> <summary>Automattic/node-canvas</summary>

v1.6.13

Compare Source

v1.6.12

Compare Source

v1.6.11

Compare Source

</details>


Renovate configuration

:date: Schedule: At any time (no schedule defined).

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

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

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


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+1 -1

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

startedkinx-project/mk66f-hw

started time in 23 days

startedstatping/statping

started time in 23 days

PR closed elsbrock/logstash-docker

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • Dockerfile (dockerfile)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

<details> <summary>Update phusion/baseimage Docker tag to v0.10.2</summary>

  • Schedule: ["at any time"]
  • Branch name: renovate/docker-phusion-baseimage-0.x
  • Merge into: master
  • Upgrade phusion/baseimage to 0.10.2

</details>


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


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

+5 -0

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

delete branch elsbrock/tilejson-dl

delete branch : renovate/npm-canvas-vulnerability

delete time in 23 days

push eventelsbrock/tilejson-dl

Renovate Bot

commit sha 47ac9dd94fdecd1b1ac1174eccc45996c626fb09

Update dependency canvas to v1.6.10 [SECURITY]

view details

Simon Elsbrock

commit sha ad47b802fee4c43478a54d10bb4fd7723f442c73

Merge pull request #4 from elsbrock/renovate/npm-canvas-vulnerability Update dependency canvas to v1.6.10 [SECURITY]

view details

push time in 23 days

PR merged elsbrock/tilejson-dl

Update dependency canvas to v1.6.10 [SECURITY]

This PR contains the following updates:

Package Type Update Change
canvas dependencies minor 1.3.16 -> 1.6.10

GitHub Vulnerability Alerts

GHSA-vpq5-4rc8-c222 / WS-2019-0048

Versions of canvas prior to 1.6.10 are vulnerable to Denial of Service. Processing malicious JPEGs or GIFs could crash the node process.


Release Notes

<details> <summary>Automattic/node-canvas</summary>

v1.6.10

Compare Source

v1.6.9

Compare Source

==================

Fixed

v1.6.8

Compare Source

==================

Fixed

v1.6.7

Compare Source

==================

Fixed

v1.6.6

Compare Source

==================

Fixed
  • Use .node extension for requiring native module so webpack works (1b05599)
  • Correct text baseline calculation (#​1037)

v1.6.5

Compare Source

==================

Changed
  • Parse font using parse-css-font and units-css (d316416)

v1.6.4

Compare Source

==================

Fixed
  • Make sure Canvas#toDataURL is always async if callback is passed (8586d72)

v1.6.3

Compare Source

==================

Fixed
  • Fix isnan() and isinf() on clang (5941e13)

v1.6.2

Compare Source

==================

Fixed

v1.6.1

Compare Source

==================

Fixed
  • Make has_lib.sh work on BSD OSes (1727d66)

v1.6.0

Compare Source

==================

  • Support canvas.getBuffer('raw') (#​819)

v1.5.0

Compare Source

==================

  • Crude PDF stream implementation (#​781)
  • Update CI settings (#​797)
  • Reduce some of the install warnings (#​794)
  • Fix lineDash browser tests never finishing (#​793)
  • Add issue template (#​791)

v1.4.0

Compare Source

==================

  • Add support for evenodd fill rule (#​762)

</details>


Renovate configuration

:date: Schedule: "" (UTC).

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

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

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


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+1 -1

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

push eventelsbrock/tilejson-dl

Renovate Bot

commit sha c33df2c75db16f8511ae26efc681ec0c4bb0b459

Pin dependencies

view details

Simon Elsbrock

commit sha 5321e8d63cc0f406a7e88fb2df63acf60f37821c

Merge pull request #2 from elsbrock/renovate/pin-dependencies Pin dependencies

view details

push time in 23 days

PR merged elsbrock/tilejson-dl

Pin dependencies

This PR contains the following updates:

Package Type Update Change
canvas dependencies pin ~1.3.10 -> 1.3.16
tilejson dependencies pin ~1.0.1 -> 1.0.3

:pushpin: Important: Renovate will wait until you have merged this Pin PR before creating any upgrade PRs for the affected packages. Add the preset :preserveSemverRanges your config if you instead don't wish to pin dependencies.


Renovate configuration

:date: Schedule: At any time (no schedule defined).

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

:recycle: Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+2 -2

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

PR closed elsbrock/docker-container

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • mopidy-stream/Dockerfile (dockerfile)
  • rifec/Dockerfile (dockerfile)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


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

+5 -0

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

delete branch elsbrock/tilejson-dl

delete branch : renovate/configure

delete time in 23 days

push eventelsbrock/tilejson-dl

Renovate Bot

commit sha 1e1f457f0f00fa8b81470017000530ab42d3a43e

Add renovate.json

view details

Simon Elsbrock

commit sha 323ba13bc68aed51a724e0764f09c5d90c6bbbea

Merge pull request #1 from elsbrock/renovate/configure Configure Renovate

view details

push time in 23 days

PR merged elsbrock/tilejson-dl

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • package.json (npm)
  • .travis.yml (travis)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

<details> <summary>Pin dependencies</summary>

  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: master
  • Pin canvas to 1.3.16
  • Pin tilejson to 1.0.3

</details>

<details> <summary>Update dependency canvas to v1.6.13 [SECURITY]</summary>

  • Branch name: renovate/npm-canvas-vulnerability
  • Merge into: master
  • Upgrade canvas to 1.6.13

</details>


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


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

+5 -0

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

PR closed elsbrock/twitblock

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • requirements.txt (pip_requirements)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

<details> <summary>Pin dependencies</summary>

  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: master
  • Pin PyPDF2 to ==1.26.0
  • Pin python_twitter to ==3.3

</details>

<details> <summary>Update dependency python_twitter to v3.5</summary>

  • Schedule: ["at any time"]
  • Branch name: renovate/python_twitter-3.x
  • Merge into: master
  • Upgrade python_twitter to ==3.5

</details>


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


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

+5 -0

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

push eventelsbrock/go-ghwrite

Renovate Bot

commit sha 0b5158de4c4fe8785d4082dfdb77545b3787a7f1

chore(deps): add renovate.json

view details

Simon Elsbrock

commit sha 3daf13f591d2b75a2165fe0370a412a769cebdc2

Merge pull request #1 from elsbrock/renovate/configure Configure Renovate

view details

push time in 23 days

delete branch elsbrock/go-ghwrite

delete branch : renovate/configure

delete time in 23 days

PR merged elsbrock/go-ghwrite

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • go.mod (gomod)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


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

+5 -0

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

PR closed elsbrock/docker-weechat

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • Dockerfile (dockerfile)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

<details> <summary>Update phusion/baseimage Docker tag to v0.10.2</summary>

  • Schedule: ["at any time"]
  • Branch name: renovate/docker-phusion-baseimage-0.x
  • Merge into: master
  • Upgrade phusion/baseimage to 0.10.2

</details>


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


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

+5 -0

0 comment

1 changed file

renovate[bot]

pr closed time in 23 days

push eventelsbrock/edgerouter-backup

Simon Elsbrock

commit sha 08cd6d90f5c9d7c8440cce2a5114c2e878f499d2

initial commit

view details

push time in 24 days

push eventelsbrock/edgerouter-backup

Simon Elsbrock

commit sha 26ad6c48b1379fde3658b16be50a0edafbd13029

by else via other

view details

push time in 24 days

push eventelsbrock/edgerouter-backup

Simon Elsbrock

commit sha d37db9ac85fc5ad0ed0b054f6afb8095f2106d73

chore: make script work

view details

push time in 24 days

PublicEvent

push eventelsbrock/edgerouter-backup

Simon Elsbrock

commit sha fedd19dd4267046f9236e1d78754c0cb327f2421

fix: heredoc

view details

Simon Elsbrock

commit sha 5a2410f1a24a7e73db6c533b9011cd632497aab0

chore: gosh, i'm so bad with shell

view details

push time in 24 days

push eventelsbrock/edgerouter-backup

Simon Elsbrock

commit sha 5109edd96b13b7d415ae03dd9b7b2ca4e86345ab

chore: eeerm, logic 101

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha f540f229c4c2643428632d6286446487d40da1be

docs: add build status

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 42f8348682ec807b4df5faaf5252f216c8381d22

fix: missing path var

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha b818252dd802c5fadf9b14078c35da9516e13467

docs: fix typo

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 6db433624fde418bd5b9be25da3b13ef43cdef1a

fix: formatting of output

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha ccd892886630c4649d33b6c0826abc819bb0e301

docs: limitations

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 1a47505a3fea6942acbbdc218b9c3497752a1c6e

docs: add README

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 06fb3fcc7500a30b62b3e55497cbe785618cdb58

chore: add build

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha dcd5eeb1b62b18b91c8d22e2d5008c35fa236c29

Update release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha d6ac6f545000c250885925d544fd8b14571d8781

chore: add build

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 6e52464f675327ee7c00d78ccb34e57a43ac2e44

Update release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 3b11f73c7864f3905d5cd80fe689e0cb1b217aca

Update release.yml

view details

push time in 24 days

created tagelsbrock/go-ghwrite

tagv0.1.0

Write to file in Github repo using the GH File API

created time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 34e2e33df92ea15f7d9595c09aa5616c24fa9a4c

Update release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 11664b107b54ed94329845488f64a6a365e15522

Update release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 0c28f59765d9bcbfc4242841534d5ce73880ed9f

Update release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 8e84d8c48a0de4d6743998819d2220b301c8d3ce

Update go.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 9a53acde3d31f66f4128db2bdac2ac9f0e9d2550

Update go.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 2cf4f0e0e49a80ba0cda1543c7b078f0a619ec53

fix: build: upload artifacts

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 9df6f73d8574c46a7189304fba51ac0654600257

feat: upload artifact

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 1ddf2ccda28944ca29125fbf82b306145324f354

Update go.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 834b2da41b0551959e75eec5452d23c7d17df500

Update release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 53ce7e1b250143563ca4cfcf2470cfe6b8b90319

Create release.yml

view details

push time in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha 1a9dab40f7fb4a26c89e6e79953917e280d39c97

Create go.yml

view details

push time in 24 days

fork elsbrock/gokrazy

a pure-Go userland for your Raspberry Pi 3 appliances

https://gokrazy.org

fork in 24 days

push eventelsbrock/go-ghwrite

Simon Elsbrock

commit sha c401fafe7c98ece8c61cd4228320e0974c261c4d

chore: default user and email to token owner

view details

Simon Elsbrock

commit sha 744622095678a918cba528be02df7de70f3a376f

feat: add support for writing tarballs

view details

push time in 25 days

startedkibitzr/kibitzr

started time in a month

more