Repository navigation
Tags
Tags
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
ci(fork-release): derive sidecar build command from upstream's bundler Upstream added a buzz-backend-kubernetes sidecar in 0.5.4, so the hardcoded `cargo build -p ...` list stopped producing everything bundle-sidecars.sh now requires, failing both platform builds. Instead of tracking the package list here, extract the build command from scripts/bundle-sidecars.sh of the checked-out upstream tag. The script's own BUILD_HINT always names exactly the packages it checks, so this keeps working for older tags and future sidecar additions. Co-Authored-By: Craft Agent <agents-noreply@craft.do>
PreviousNext