fix(ci): revert TechDocs workflow to v11.1.0 to fix publish failure - #333
Merged
Conversation
size-limit report 📦
|
maximizeIT
force-pushed
the
fix/revert-techdocs-workflow-version
branch
from
September 10, 2026 08:55
222266b to
3ea6e54
Compare
…failure v16.0.0 uses Staffbase/backstage-techdocs-action@v0.2.4, which added strict input validation. It fails with: storage-name, azure-account-name, and azure-account-key are required for Azure Blob Storage publishing Confirmed via the GitHub API (organization-variables endpoint) that the org variable TECHDOCS_AZURE_ACCOUNT_NAME is not scoped/visible to this repo, unlike e.g. cc-custom-plugin-applaunchpad, which has it. Pinning to a different template version (e.g. v15.1.1) would not help since that also uses backstage-techdocs-action@v0.2.4. v11.1.0 uses the older action v0.2.2, which gates the Azure publish step behind an 'if azure-account-name != ***' check and skips it silently instead of failing. This keeps the pipeline green but does not restore actual TechDocs publishing for this repo - that requires an org admin to scope TECHDOCS_AZURE_ACCOUNT_NAME to plugins-client-sdk. Run: https://github.com/Staffbase/plugins-client-sdk/actions/runs/34456165077 Co-authored-by: GitHub Copilot <copilot@noreply.github.com>
maximizeIT
force-pushed
the
fix/revert-techdocs-workflow-version
branch
from
September 10, 2026 08:56
3ea6e54 to
b91e927
Compare
maximizeIT
marked this pull request as ready for review
September 10, 2026 08:58
ingvaar
approved these changes
Sep 10, 2026
|
🎉 This PR is included in version 3.1.5 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
2 participants
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
Fixes the TechDocs publish failure introduced by #331's GitHub Actions bump. See failing run: https://github.com/Staffbase/plugins-client-sdk/actions/runs/34456165077/job/102802932758
Root cause (confirmed)
#331 bumped
.github/workflows/techdocs.yml's reusable workflow reference fromv11.1.0tov16.0.0. That template usesStaffbase/backstage-techdocs-action@v0.2.4, which added a strict input-validation step that fails with:I confirmed via the GitHub API that this is not a template-version issue — it's an org-variable visibility gap:
cc-custom-plugin-applaunchpad'stechdocs.ymlis pinned tov15.1.1, which also usesbackstage-techdocs-action@v0.2.4(identical SHA) — so pinning to that version instead would not avoid the failure.applaunchpadonly succeeds because its repo has org-variable access thatplugins-client-sdkcurrently lacks.Fix (stopgap, not a real fix)
Reverted
template_techdocs.ymlback tov11.1.0, which uses the olderbackstage-techdocs-action@v0.2.2. That version gates the Azure publish step behindif: azure-account-name != ''and silently skips it instead of failing when the var is empty. This keeps the pipeline green, but TechDocs still won't actually publish for this repo until the underlying gap is fixed — it's very possible this has been silently no-op'ing for a while already.All other action bumps from #331 (checkout, setup-node, create-github-app-token, semantic-release-action, yarn-lock-changes) are untouched and unaffected.
Real fix needed (not in this PR, requires org-admin access)
An org admin needs to add
plugins-client-sdkto theTECHDOCS_AZURE_ACCOUNT_NAMEorganization variable's repository scope. Once that's done,template_techdocs.ymlcan be safely re-bumped tov16.0.0(or later) and TechDocs will actually publish again.🤖 Generated with assistance from GitHub Copilot.