build(deps): bump actions/download-artifact to v8.0.2
User description
Summary
- Update every
actions/download-artifactreference inci.yml,mutation.yml, andtauri-build.ymlfrom v8.0.1 to v8.0.2, pinned to immutable commit9000827ccba6bdab643e8b6fd33ac0654aef8333. - This is the narrow current-main successor for Dependabot PR #1051, whose original checks were against an older main base.
Upstream and workflow review
- GitHub reports the target commit's signature as verified; the official
v8.0.2release is non-draft/non-prerelease and was published 2026-10-07. - The upstream patch release improves download retries for HTTP 429 and valid
Retry-Afterheaders and updates@actions/artifactto 6.3.1. The action runtime remains Node 24, matching the pinned v8.0.1 action. - All three repository references were enumerated and updated; no sibling
uses:path remains on the old SHA.
Validation
- Local frozen dependency reconcile, signing doctor, outgoing signature/attribution checks, PR budget, and
ci:prepushpassed on this exact one-commit branch. The local gate failed closed to full admission (AMBIGUOUS) and all local checks passed. - Full hosted CI, CodeQL/security, reviewer governance, and independent review are required on this exact head before merge.
Summary by Sourcery
Update artifact downloads to the verified v8.0.2 action release across CI workflows.
CI:
- Update all GitHub Actions workflows to use the immutable v8.0.2 release of
actions/download-artifact. - Adopt the upstream patch release with improved retry handling for rate-limited artifact downloads.
Summary by cubic
Bumps actions/download-artifact from v8.0.1 to v8.0.2 in all three workflows, pinned to the verified v8.0.2 release commit. The patch improves download retries for HTTP 429 responses with valid Retry-After headers and updates @actions/artifact to 6.3.1.
CodeAnt-AI Description
Make CI artifact downloads more reliable during rate limits
What Changed
- CI, mutation-report, and release workflows use an updated artifact downloader that retries rate-limited downloads.
Impact
✅ Fewer CI failures from artifact download rate limits
✅ More reliable browser test runs
✅ More reliable release bundle assembly
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit
- Chores
- Updated the pinned artifact download action used in CI, mutation testing, and release workflows.