Skip to content

Use Tropibot-authenticated builds for package harness testing - #11

Merged
3alpha merged 1 commit into
mainfrom
fix/immich-harness-build
Nov 4, 2026
Merged

3alpha merged 1 commit into
mainfrom
fix/immich-harness-build

Conversation

@3alpha

@3alpha 3alpha commented Nov 4, 2026

Copy link
Copy Markdown
Member

The current package build posts its SDK artifact comment as github-actions[bot]. Tropibot's package-harness coordinator accepts build comments only from the configured Tropibot bot and matching GitHub App ID, so successful builds do not enqueue harness tests.

Use the shared dappnode-build-hash.yml workflow, which creates a Tropibot app token and passes it to the SDK. Match the non-main branch push trigger used by sibling packages to avoid duplicate artifact builds. Inherit the existing organization secrets and grant the caller the permissions required by the reusable workflow.

Validation: compared with the live shared workflow and n8n's build workflow; checked YAML structure, triggers, permissions, and git diff --check. Hosted verification should produce a tropibot[bot] build comment for this PR's head and enqueue a package-harness job.

@3alpha
3alpha merged commit 227688f into main Nov 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant