ci: skip search-data generation when GEMINI_API_KEY is missing - #186
Merged
Conversation
The updater failed silently-in-a-corner every week since 2026-06-14 because the repo secret vanished — icon updates were hostage to the search-data step. Skip description generation (with a loud log line) when the key is absent; new icons just lag in semantic search until the key returns. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Part of a cross-repo change (mmacpherson/mikemac#90): PR-producing workflows open (or comment on) a 'ci-failure'-labeled issue on failure so a dead updater can't masquerade as a quiet week — this exact workflow was dead for 5 weeks before anyone noticed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Added a second commit: both housekeeping workflows now auto-file a |
… failure The skip-guard made a missing key produce a green run with a buried log warning — the same invisibility that hid the original outage. Missing key now files/comments the ci-failure issue (with the sops recovery pointer) while still letting the icon update land. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The weekly Lucide updater has failed since 2026-06-14 because the GEMINI_API_KEY repo secret disappeared — and the hard failure in the search-data step blocked icon updates entirely (we fell from 1.17.0 to 8 releases behind).
This makes the description-generation step skip loudly instead of fail when the key is absent: icon updates always land; new icons simply lag in semantic search until a key is restored. (The key has been re-provisioned separately, so this is belt-and-suspenders.)
🤖 Generated with Claude Code