feat: split stack property into per-builder properties

The `stack` property lived on the `buildpacks` plugin but was shared by both the herokuish and pack builders, so a value valid for one builder broke the other. Each builder now owns its own `stack` property managed via `builder-herokuish:set` and `builder-pack:set`, while `buildpacks:set-property stack` is deprecated and forwards the value to the builder detected from it; existing values migrate automatically on upgrade and changing a builder's stack clears that builder's cache.
This commit is contained in:
Jose Diaz-Gonzalez committed 2026-11-02 16:48:11 -05:00
1 parent 5ef061d3d2
commit 59594937f9
23 files changed
+449 -178

No files matched your search

@@ -28,3 +28,27 @@ fn-builder-herokuish-allowed() {
fn-plugin-property-get-default "builder-herokuish" "$APP" "allowed" ""
}
fn-builder-herokuish-computed-stack() {
declare APP="$1"
stack="$(fn-builder-herokuish-stack "$APP")"
if [[ -z "$stack" ]]; then
stack="$(fn-builder-herokuish-global-stack "$APP")"
fi
if [[ -z "$stack" ]]; then
stack="${DOKKU_IMAGE:-gliderlabs/herokuish:latest-24}"
fi
echo "$stack"
}
fn-builder-herokuish-global-stack() {
fn-plugin-property-get-default "builder-herokuish" "--global" "stack" ""
}
fn-builder-herokuish-stack() {
declare APP="$1"
fn-plugin-property-get-default "builder-herokuish" "$APP" "stack" ""
}