From 17570f06691de75b3befa90a8ed05d2bac435075 Mon Sep 17 00:00:00 2001 From: Maxim Kalina Date: Thu, 14 May 2026 11:55:56 +0200 Subject: [PATCH] =?UTF-8?q?chore(renovate):=20never=20bump=20io.plugwerk?= =?UTF-8?q?=20SDK=20pins=20=E2=80=94=20examples=20must=20track=20latest=20?= =?UTF-8?q?SNAPSHOT?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both gradle/libs.versions.toml pin plugwerk = "1.0.0-SNAPSHOT" by design so day-to-day development tests against the latest Plugwerk server build and surfaces upstream regressions early (e.g. SPI breaking changes land in the SNAPSHOT first, examples catch them before downstream users do). Renovate just opened #44 to bump to v1.0.0 (the freshly released stable), which would freeze the test target. Add an ignore rule for io.plugwerk:** on the maven datasource so future SDK releases don't generate the same PR again. Manual bump to a fixed release stays an explicit step at examples- repo release time. --- .github/renovate.json | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/renovate.json b/.github/renovate.json index e4986a9..6ab890e 100644 --- a/.github/renovate.json +++ b/.github/renovate.json @@ -1,4 +1,12 @@ { "$schema": "https://docs.renovatebot.com/renovate-schema.json", - "extends": ["github>plugwerk/.github"] + "extends": ["github>plugwerk/.github"], + "packageRules": [ + { + "description": "The examples must always build against the latest Plugwerk SNAPSHOT to surface upstream regressions early. Pinning to a released version (e.g. 1.0.0) would defeat that. The pin is bumped manually only when an examples-repo release of the same name is cut.", + "matchDatasources": ["maven"], + "matchPackageNames": ["io.plugwerk:**"], + "enabled": false + } + ] }