Update actions/download-artifact action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/download-artifact	action	major	v6 -> v7

---

Release Notes

actions/download-artifact (actions/download-artifact)

v7

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5026b7a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This pull request updates the actions/download-artifact action in the integrity_check job of the .github/workflows/release-cycle.yml file from version 6 to version 7. The update affects the step responsible for downloading the tarball artifact. No other modifications are made to the workflow configuration or other job steps.

Possibly related PRs

• Update actions/download-artifact action to v6 - autoclosed #6017: Previous version bump of the same actions/download-artifact action step from v5 to v6, representing a sequential dependency update to the same workflow component.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately summarizes the main change: updating the actions/download-artifact action from v6 to v7.
Description check	✅ Passed	The description provides relevant details about the update, including the package name, update type, version change, and release notes reference.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/actions-download-artifact-7.x

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 79e4988 and 536e45f.

📒 Files selected for processing (1)

• .github/workflows/release-cycle.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)

• GitHub Check: boostsecurity - boostsecurityio/scanner
• GitHub Check: Redirect rules - solidity-contracts
• GitHub Check: Header rules - solidity-contracts
• GitHub Check: Pages changed - solidity-contracts
• GitHub Check: slither
• GitHub Check: tests-upgradeable
• GitHub Check: tests
• GitHub Check: tests-foundry
• GitHub Check: coverage
• GitHub Check: halmos

🔇 Additional comments (1)

.github/workflows/release-cycle.yml (1)

170-179: Verify compatibility with the actions/upload-artifact version.

The v7 release now runs on Node.js 24, and requires a minimum Actions Runner version of 2.327.1. Since the workflow uses GitHub-hosted runners (ubuntu-latest), this should be automatically satisfied. However, ensure the artifact format uploaded by actions/upload-artifact@v5 (line 147) remains compatible with download-artifact@v7's expectations.

The output variable ${{ steps.artifact.outputs.download-path }} (line 179) should remain available in v7, but verify this doesn't change by checking the v7 release notes or running a test workflow to confirm the artifact is located correctly.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}