Merged
Conversation
Contributor
|
@dependabot recreate |
Bumps [undici](https://github.com/nodejs/undici) from 6.0.1 to 6.2.1. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v6.0.1...v6.2.1) --- updated-dependencies: - dependency-name: undici dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
72bb4f4 to
b6e5c85
Compare
JamesMGreene
approved these changes
Dec 22, 2023
cyrilmourin
added a commit
to cyrilmourin/veille-parlementaire-sport
that referenced
this pull request
Apr 23, 2026
… upload
Symptome observe sur collect-and-publish (runs R23-D2 et R23-E) :
Error: Multiple artifacts named 'github-pages' were unexpectedly
found for this workflow run. Artifact count is 3.
at getArtifactMetadata (actions/deploy-pages/v4)
at Deployment.create
Cause :
Le job unique 'collect-and-publish' n'appelle upload-pages-artifact
qu'une seule fois. MAIS le bug connu actions/deploy-pages#290 veut
que si l'utilisateur clique 'Re-run failed jobs' sur un run existant,
GitHub Actions relance les steps en echec SANS purger les artefacts
deja publies par le run initial. A la 2e tentative, il y a 2
artefacts 'github-pages' pour le meme run_id ; a la 3e, 3. Le step
deploy-pages@v4 lit la liste des artefacts du run courant, en trouve
plusieurs avec le meme nom, et abandonne avec l'erreur ci-dessus.
Fix (.github/workflows/daily.yml) :
Nouveau step 'Purge stale github-pages artifacts from this run' INSERE
juste avant 'Upload Pages artifact'. Il utilise actions/github-script@v7
pour :
1. lister les artefacts du run courant (context.runId) via l'API
REST GitHub ;
2. filtrer sur name == 'github-pages' ;
3. les supprimer un par un via deleteArtifact.
Le step ne touche a rien au premier passage (pas d'artefact encore) et
purge les stales sur tout re-run. upload-pages-artifact re-ecrit
ensuite l'artefact unique que deploy-pages consomme.
Effet :
- Premier run : aucun artefact à purger, upload normal, deploy OK.
- Re-run failed jobs : purge des 1-N artefacts stales avant upload,
deploy-pages@v4 trouve un unique 'github-pages', deploy OK.
- Aucun impact sur les autres artefacts (digest-${run_id}, caches…).
Permissions :
Ajout d'actions: write dans le bloc 'permissions:' du workflow.
deleteArtifact() exige cette permission ; sans elle, le step
renvoie 403 et bloque le deploy. Le bloc passe donc de
contents: write / pages: write / id-token: write
a
contents: write / pages: write / id-token: write / actions: write
Pas de test automatise : on ne teste pas les workflows GHA. Validation
en conditions reelles sur le prochain re-run.
Ref : actions/deploy-pages#290
cyrilmourin
added a commit
to cyrilmourin/veille-parlementaire-sport
that referenced
this pull request
Apr 23, 2026
… upload
Symptome observe sur collect-and-publish (runs R23-D2 et R23-E) :
Error: Multiple artifacts named 'github-pages' were unexpectedly
found for this workflow run. Artifact count is 3.
at getArtifactMetadata (actions/deploy-pages/v4)
at Deployment.create
Cause :
Le job unique 'collect-and-publish' n'appelle upload-pages-artifact
qu'une seule fois. MAIS le bug connu actions/deploy-pages#290 veut
que si l'utilisateur clique 'Re-run failed jobs' sur un run existant,
GitHub Actions relance les steps en echec SANS purger les artefacts
deja publies par le run initial. A la 2e tentative, il y a 2
artefacts 'github-pages' pour le meme run_id ; a la 3e, 3. Le step
deploy-pages@v4 lit la liste des artefacts du run courant, en trouve
plusieurs avec le meme nom, et abandonne avec l'erreur ci-dessus.
Fix (.github/workflows/daily.yml) :
Nouveau step 'Purge stale github-pages artifacts from this run' INSERE
juste avant 'Upload Pages artifact'. Il utilise actions/github-script@v7
pour :
1. lister les artefacts du run courant (context.runId) via l'API
REST GitHub ;
2. filtrer sur name == 'github-pages' ;
3. les supprimer un par un via deleteArtifact.
Le step ne touche a rien au premier passage (pas d'artefact encore) et
purge les stales sur tout re-run. upload-pages-artifact re-ecrit
ensuite l'artefact unique que deploy-pages consomme.
Effet :
- Premier run : aucun artefact à purger, upload normal, deploy OK.
- Re-run failed jobs : purge des 1-N artefacts stales avant upload,
deploy-pages@v4 trouve un unique 'github-pages', deploy OK.
- Aucun impact sur les autres artefacts (digest-${run_id}, caches…).
Permissions :
Ajout d'actions: write dans le bloc 'permissions:' du workflow.
deleteArtifact() exige cette permission ; sans elle, le step
renvoie 403 et bloque le deploy. Le bloc passe donc de
contents: write / pages: write / id-token: write
a
contents: write / pages: write / id-token: write / actions: write
Pas de test automatise : on ne teste pas les workflows GHA. Validation
en conditions reelles sur le prochain re-run.
Ref : actions/deploy-pages#290
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
1 participant
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.
Bumps undici from 6.0.1 to 6.2.1.
Release notes
Sourced from undici's releases.
Commits
f51f917Bumped v6.2.136e8131Remove timers in agent.js (#2536)5f4d435chore: reduce dependencies (#2533)c5c6648perf: use tree (#2528)0c4c450Bumped v6.2.059c2f38Remove FinalizationRegistry from Agent (#2530)250b89aBumped v6.1.038f2226feat: expose headerNameToString (#2525)974a85eCall fg.unregister() after a dispatcher is done, adds UNDICI_NO_FG to… (#2527)871baa7feat: Add resource timing entries for connection, request and response (#2481)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)