Conversation
size-limit report 📦
|
ingvaar
force-pushed
the
fix/techdocs-revert
branch
from
September 14, 2026 12:43
2469a59 to
dcabf12
Compare
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.
Summary
Restores the pin that #333 put in place. #334 bumped
template_techdocs.ymlfrom v11.1.0 to v17.0.1 and main has been red onpublish-techdocs-site / TechDocssince it merged.Root cause
Same one #333 already diagnosed, so this is not a new problem. v16.0.0 and later reach
backstage-techdocs-action@v0.2.4, which added a strict validation step. In this repovars.TECHDOCS_AZURE_ACCOUNT_NAMEresolves to an empty string, so the job fails with:Confirmed the variable genuinely isn't visible here:
The template's inputs are all
required: falsewith defaults, so the caller signature was never the issue. It's purely the org variable scoping.Note
There's no dependabot ignore rule for this template, so the bump will come back next week and someone will merge it again, exactly like #331 → #333 → #334. Worth adding one, but I've kept this PR to the revert only as discussed.
The real fix is scoping
TECHDOCS_AZURE_ACCOUNT_NAMEto this repository, after which the pin can be lifted for good.