mirror of
https://github.com/basecamp/once-campfire.git
synced 2026-08-26 16:50:52 +09:00
431aad8b71
The base image tag is a build arg — `ARG RUBY_VERSION` plus `FROM ruby:$RUBY_VERSION-slim` — and Dependabot's docker updater matches literal tags, so this entry has never had anything to propose. It ran green every week and reported nothing, which reads as coverage and isn't. No other repo in the fleet configures a docker ecosystem, and none could: they all either interpolate a variable or pull from the internal registry. Inlining the tag here to buy coverage would make this Dockerfile the outlier instead, against Rails-generated boilerplate. Ruby bumps stay a manual, human-decided step.
32 lines
881 B
YAML
32 lines
881 B
YAML
version: 2
|
|
updates:
|
|
- package-ecosystem: github-actions
|
|
directory: "/"
|
|
groups:
|
|
github-actions:
|
|
patterns:
|
|
- "*"
|
|
schedule:
|
|
interval: weekly
|
|
cooldown:
|
|
default-days: 7
|
|
|
|
- package-ecosystem: bundler
|
|
directory: "/"
|
|
schedule:
|
|
interval: weekly
|
|
cooldown:
|
|
semver-major-days: 7
|
|
semver-minor-days: 3
|
|
semver-patch-days: 2
|
|
default-days: 7
|
|
exclude:
|
|
- "brakeman"
|
|
|
|
# No docker ecosystem. Our base image tag is a build arg
|
|
# (`FROM ruby:$RUBY_VERSION-slim`), which the updater cannot read, so the
|
|
# entry only ever matched nothing — worse than no entry, because it looked
|
|
# like coverage. Ruby base image bumps are a manual, reviewed step here, as
|
|
# they are across the rest of the fleet. Keep Dockerfile, Dockerfile-export
|
|
# and .ruby-version on the same version by hand.
|