Hints about service version tracking

This commit is contained in:
Erich Blume 2026-04-13 08:40:49 -07:00
commit fca3010042
2 changed files with 6 additions and 3 deletions

View file

@ -1,4 +1,9 @@
[tools]
# Versions set here are referenced against service-versions.yaml
# If you add a new tool, please:
# 1. pin a specific version (or even better, a SHA)
# 2. create a new entry in service-versions.yaml
# This will help ensure reviewed upgrades at a steady cadence
"pipx:ansible-core" = { version = "2.20.1", uvx = "true", uvx_args = "--with botocore --with boto3" }
prek = "0.3.4"
pulumi = "3.215.0"

View file

@ -1,4 +1,4 @@
# Service Version Tracking
# Service / Tooling/ Application Version Tracking
#
# Tracks when each BlumeOps service was last reviewed for version freshness.
# Used by `mise run service-review` to surface stale services.
@ -394,8 +394,6 @@ services:
upstream-source: https://github.com/grafana/alloy/releases
notes: COPY --from in fly/Dockerfile for log shipping and metrics
# --- Mise-managed development tools ---
- name: dagger
type: mise
last-reviewed: 2026-04-12