Repository navigation
ci: automerge low-risk Renovate updates, keep the MQTT path manual - #22
Merged
Merged
Conversation
Automerges non-major CI tooling, golang image patches and Go module patches (grouped weekly), once CI passes. The MQTT client, the Go toolchain and all majors stay manual. Pins Actions to digests and validates the Renovate config in CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every Renovate PR here was merged by hand, though CI (test, lint, chart, image) already covers them; #19, #20, #21 were all green. A merge doesn't deploy: a
fix(deps)merge cuts a release, which reaches the flat only via a manual smart-home PR (e.g. #20 → v0.5.1 → smart-home #81). So low-risk updates can automerge here while the deploy stays gated.What
.github/renovate.json:ci.yaml(minor, patch, digest pins);golangimage patches (chore(deps), no release); Go module patches except the MQTT client, grouped into one weekly PR (so at most one release a week).github.com/eclipse/paho.mqtt.golang(carries every TRV command; labelheating-path, 7 days release age), thegodirective/toolchain, all majors (labelmajor).minimumReleaseAge3 days, one Saturday batch,gomodTidy,platformAutomerge: false(main has no required checks yet, so GitHub auto-merge would not wait for CI).helpers:pinGitHubActionDigests: pins Actions to commit SHAs. A moved tag can no longer change what runs in the release job withpackages: write..github/workflows/ci.yaml: newrenovate-configjob (PRs only) runningrenovate-config-validator --strict. It's not inneedsofrelease.ci:commits: svu doesn't cut a release for this.How to validate
CI green on this PR, including
renovate-config. After merge, expect a PR pinning the Actions to digests that automerges in the 09:00-18:00 window.Risk / rollback
An automerged Go patch could break the service at runtime that tests don't cover. It would still need the manual smart-home chart PR to reach the flat. Rollback: revert this PR.
🤖 Generated with Claude Code