Pin platform 0.1.0 release and wire up automatic propagation
build-and-publish / build (push) Failing after 1m17s

- parent/BOM now point at the immutable 0.1.0 release instead of a SNAPSHOT
- declare the Gitea Maven registry so Renovate can discover new platform versions
- renovate.json: group platform bumps into one automerged PR
- CI: drop --no-cache (releases are immutable, so caching is safe again) and add
  workflow_dispatch so rebuild-all-apps.sh can force an urgent rebuild

Co-Authored-By: Claude Opus 4.8 <[email protected]>
Claude-Session: https://claude.ai/code/session_01XXKjx7FNyRVAjU8dgB5KhN
This commit is contained in:
2026-07-22 21:03:06 -05:00
co-authored by Claude Opus 4.8
parent 2a0dd1ae6b
commit 2b772d2931
3 changed files with 36 additions and 6 deletions
+15
View File
@@ -0,0 +1,15 @@
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": ["config:recommended"],
"packageRules": [
{
"description": "Bennett platform releases: our own code, already tested and Trivy-scanned before publish. Group the parent + BOM + starters into one PR and merge it automatically so security fixes reach this app without manual work. Merging main triggers the build, which re-runs tests and re-scans; if either fails no image is pushed, so a bad bump can't reach production.",
"matchPackageNames": ["net.thebennett.platform:**"],
"groupName": "bennett platform",
"automerge": true
}
],
"vulnerabilityAlerts": {
"labels": ["security"]
}
}