From f927e1cb3593654b7af956227ee710b9e3a33941 Mon Sep 17 00:00:00 2001 From: Manu Garg Date: Thu, 25 Jun 2026 14:31:05 -0700 Subject: [PATCH] Document SonarCloud token rotation in sonar.yml The SONAR_TOKEN secret expires (~1 year max) and this repo changes infrequently, so it lapses unnoticed and breaks the next run. Add the rotation steps as a comment header where you land when the check fails. Co-Authored-By: Claude Opus 4.8 --- .github/workflows/sonar.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/workflows/sonar.yml b/.github/workflows/sonar.yml index 53ca033..6660b80 100644 --- a/.github/workflows/sonar.yml +++ b/.github/workflows/sonar.yml @@ -1,3 +1,14 @@ +# SonarCloud analysis. Auth uses the SONAR_TOKEN repo secret, which expires +# (SonarCloud caps token lifetime at ~1 year). Because this repo changes +# infrequently, the token often expires unnoticed and the next push/PR fails +# here. C/C++ requires this token-based CI analysis, so the token can't be +# dropped. To rotate it: +# 1. Generate a new token at https://sonarcloud.io/account/security +# (type: Project Analysis Token, project: manugarg_pacparser, max expiry). +# 2. Update the repo secret: +# gh secret set SONAR_TOKEN --repo manugarg/pacparser +# (or GitHub UI: Settings > Secrets and variables > Actions > SONAR_TOKEN) +# 3. Re-run this workflow (or push) to confirm the analysis passes. name: SonarCloud on: push: