Tianon Gravi d64a9e81b0 Fix behavior around `BASHBREW_LIBRARY` in GHA ... This script needs/uses a custom `BASHBREW_LIBRARY` directory, but it stores that value in the exported environment slightly too soon such that `generate-stackbrew-library.sh` picks it up (and shouldn't be). We often use "`BASHBREW_LIBRARY` is unset (or empty)" as a conditional for whether to fall back to using "https://github.com/docker-library/official-images/raw/HEAD/library/" as an explicit prefix for querying "source of truth" values for things like supported parent architectures. These two things collided in cc2dc88e04 (and similar commits) because the script saw `BASHBREW_LIBRARY` set, trusted it, but then fails to find the parent image. This is the cleanest place to fix this such that `generate-stackbrew-library.sh` can take `BASHBREW_LIBRARY` from the provided environment instead of using our generated value.		2024-09-30 11:46:48 -07:00
..
example-ci.yml	Update to actions/checkout@v4 🙃	2024-07-09 15:42:00 -07:00
generate.sh	Fix behavior around `BASHBREW_LIBRARY` in GHA	2024-09-30 11:46:48 -07:00
munge-i386.sh	Swap the platform flag too	2023-10-24 16:12:28 -07:00