* fix(github): fall back to a writable connected server's stored credential when no local server exists
Repository preparation borrowed a server's stored GitHub credential only
from the organization's canonical local server. Self-hosted setups whose
deploy target is a connected SSH server with its own stored PAT could
deploy but not scan the same private repo: with no server selected, the
fallback found no local server and preparation failed with
GITHUB_TOKEN_REQUIRED.
When no server is selected and the organization has no local server, use
the oldest connected deployment server the caller has write access to
that holds a stored token credential, the same set a real deploy can use.
Repository access, same-organization, server write permission, and
read-only local-read limits are unchanged. Explicit server selection is
unchanged.
Fixes#1630
* fix(github): require server selection for ambiguous repository credentials
* fix(dashboard): keep repository recovery server selection manual
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
Compose builds choose their own build context, so package dependencies
cannot prove a change is unrelated. Treat them like Dockerfile projects
instead of crawling the JS workspace catalog on every drift check.
Fixes#1545
* fix: queue pushes during a running deploy
A push that lands while its project is still deploying is now recorded as queued and deployed when that deployment finishes, instead of failing for good.
* fix(deploy): share durable admission for queued pushes
* fix(deploy): revalidate approvals before automatic cancellation
* test(deploy): align admission mocks and migration expectations
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
Refs #979.
When a repository has private submodules under the same owner, the App
installation token minted for the clone only covered the parent repository, so
`git submodule update` failed. The token is now re-minted to include same-owner
submodule repositories listed in .gitmodules at the deployed ref (capped at 25,
each passing the same access check as the parent). Reading .gitmodules failing
falls back to the parent-only token with a warning.
Clone URLs and GitHub tokens are redacted from clone output, error messages and
persisted deployment errors, and each resolution logs which credential source
was used (never the token itself).
A GitHub 5xx, rate limit, timeout or connection error while minting an App
installation token was swallowed by tryInstallationToken and reported as "no
credential". The chain then either fell through to a broader user credential
or ended in GITHUB_TOKEN_REQUIRED (403). The Actions runner reconciler treats
that 403 as a definitive loss of access and cancels the running job, so a
single transient GitHub error killed self-hosted runner jobs mid-run.
Transient mint failures are now rethrown. Definitive failures (suspended or
revoked installations) keep falling through as before.
Show the connected GitHub account and repository access with direct setup
actions. Share notification-channel creation with Settings and verify saved
channels without leaving the workflow draft or duplicating failed attempts.