Oliver Kieselbach b2b99e78b4 fix(ci): tolerate leading '?' in SAS token secrets ...

First real run of build-agent.yml failed the counter CAS write with
"AuthenticationFailed ... sp is mandatory": the AZURE_BLOB_AGENT_SAS_TOKEN
secret stores the query with its leading '?', and the workflow prepends
another one, so Azure saw '?sp' as the first parameter name. The pre-existing
upload step had the same latent bug -- it had just never run. Normalize with
TrimStart('?') at all three usage sites (counter, blob upload, table merge).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-17 11:00:10 +02:00

..

azure-static-web-apps-brave-grass-0070b5703.yml

ci: bump checkout to v5 in SWA workflow too (missed in cb67e8c2)

2026-06-12 16:52:42 +02:00

build-agent.yml

fix(ci): tolerate leading '?' in SAS token secrets

2026-07-17 11:00:10 +02:00

combine-rules.yml

ci: bump actions to node24-ready versions ahead of June 16 forced default

2026-06-12 16:52:01 +02:00

deploy-backend.yml

ci: switch Azure deploy login to secret-less OIDC (federated credential)

2026-07-14 17:47:25 +02:00

deploy-mcp.yml

ci: switch Azure deploy login to secret-less OIDC (federated credential)

2026-07-14 17:47:25 +02:00

indexnow-notify.yml

added valid return codes

2026-03-20 08:21:04 +01:00

oidc-login-test.yml

ci: switch Azure deploy login to secret-less OIDC (federated credential)

2026-07-14 17:47:25 +02:00