Repository navigation
Conversation
This branch has not been deployed
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 protected Android signing job failed during
setup-node: its default automatic caching detects pnpm inpackage.json, but this job has no package manager installed. Disable automatic caching for that step so signing can proceed using Node built-ins and the Android tools.Also restrict push-triggered CI to
main, retaining pull-request and manual runs. This removes duplicate feature-branch runs while preserving the exact-main-commit CI prerequisite for release packaging.Validation:
setup-nodebundle locally with Node 24.20.0 and pnpm absent: the default reproduces the missing-pnpm error;package-manager-cache: falsesucceeds.After merge and successful main CI, start a fresh manual release run to use the repaired workflow.