Repository navigation
chore(release): 0.14.1 - #611
Merged
Merged
Conversation
A custom execute_command has to carry {{ .Vars }} itself. Without it
IMAGE_REF, VERSION and SUPPORT_EMAIL were declared and never set, and the
AMI build died on 'IMAGE_REF: unbound variable' fifteen minutes in.
The existing guard asserted the declaration rather than the delivery, so it
stayed green through the failure. It now asserts the expansion.
cevheri
force-pushed
the
chore/release-0.14.1
branch
from
September 6, 2026 22:17
d25d67a to
866a577
Compare
|
6 of 20 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 0.14.1 and fixes the AMI build that has been red on main since the workflow landed.
0.14.1
The release the light theme has been waiting for. #402 landed on main after 0.14.0 was tagged: warning, success and danger text, the query editor Explain control and the monitoring status rings were all painted in colours chosen against a dark ground and reused unchanged on the light one, where the worst of them measured 1.46:1 against the surface behind it. Every accent is now a token measured on the ground it is drawn on, and the measurement runs as a test instead of being recorded in a comment. Also in the release: LOG_LEVEL documented, three docs sweeps, a Spanish README, and the AWS Marketplace AMI package.
Chart 0.1.60, appVersion 0.14.1. No template or value moves, so
artifacthub.io/changesrecords four entries andcontainsSecurityUpdatesstays false.The AMI fix
AWS AMI Buildhas failed every run withIMAGE_REF: unbound variable, fifteen minutes into the Packer build. The provisioners declareenvironment_vars, but a customexecute_commandonly delivers them where it expands{{ .Vars }}itself, andsudo -E bash '{{ .Path }}'does not. So IMAGE_REF, VERSION and SUPPORT_EMAIL were never set.The guard that was supposed to catch this asserted the declaration rather than the delivery, which is why it stayed green through every failed build. It now asserts the expansion, and it was probed against both provisioner blocks before the fix.
Gates
format, lint, typecheck, knip, chart:check, readme:check, security:check, channels:showcase:check, helm lint --strict, build, build:lib, attw, gofmt/go vet/go test, full test suite, coverage 45983/45983 (100.00%).