Repository navigation
fix(security): least-privilege tokens in docouture workflows - #20
Merged
Merged
Conversation
Resolves Scorecard Token-Permissions alerts #9-#13 on main: - docouture-release.yml:89 top-level 'contents: write' - docouture-release-preview.yml:1 no top-level permission - docouture-publish.yml:1 no top-level permission - docouture-publish.yml:53 job-level 'contents: write' - docouture-publish-prerelease.yml:131 job-level 'contents: write' Adopts the hardened versions already shipped in InditexTech/internal-ops#768 for these same docouture scaffold workflows: top-level permissions {}, job permissions content read with the gh-pages/tag pushes authenticating via the narrowed App token, explicit APP_PRIVATE_KEY instead of secrets: inherit, no dorny/paths-filter and no caches on publishing lanes. cerbia's two temporary workarounds (Build docs / Cut release) are preserved. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
❗ This Pull Request will not trigger a docs releaseA Pull Request with no |
Contributor
❌ No changes in
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
❗ This Pull Request will not trigger a docs releaseA Pull Request with no |
Contributor
Python Release Preview
ChangesFixed
|
Contributor
❗ This Pull Request will not trigger a docs releaseA Pull Request with no |
Contributor
Release PreviewThis pull request has the |
|
This was referenced Oct 14, 2026
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.
Resumen
Resuelve los 5 alertos Token-Permissions (high) de Scorecard abiertos sobre
main(#9–#13), localizados en los 4 workflowsdocouture-*introducidos por #9.Alertos resueltos
.github/workflows/docouture-release.ymlcontents: write.github/workflows/docouture-release-preview.ymlpermissions.github/workflows/docouture-publish.ymlpermissions.github/workflows/docouture-publish.ymlcontents: write.github/workflows/docouture-publish-prerelease.ymlcontents: writeQué cambia
Los 6 workflows
docouture-*adoptan el hardening ya validado en InditexTech/internal-ops#768 para el mismo scaffold:permissions: {}a nivel de workflow;contents: read(opull-requests: writesolo en los jobs de comentario) por job.gh-pages, tagsdocs/*y el bump dedocs/.release-versionya autentican con el App token, ahora acotado (owner/repositories/permission-contents: write);GITHUB_TOKENqueda read-only conpersist-credentials: false.APP_PRIVATE_KEYpasa al reusable como secret explícito en vez desecrets: inherit.dorny/paths-filter(diff git local).Los dos
TEMPORARY WORKAROUNDpropios de cerbia (Build docs / Cut release +fix-search-index.mjs) se conservan intactos.Verificación
zizmor(1.29.0, persona regular) sobre los 6 workflows: 0 hallazgos (antes 14, incl. los 5 deexcessive-permissions).