Merge Develop into Main

[Oba-One]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
green-goods	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 1, 2025 10:38pm

To fix the problem, we need to ensure that any sensitive information, such as the Etherscan API key, is not logged in clear text. The best way to do this is to update the logic that builds the displayArgs array so that it also redacts the value of the --etherscan-api-key argument, replacing it with [REDACTED] just as is done for the private key. This change should be made in the executeForgeScript method, specifically in the mapping function that creates displayArgs (lines 959–960). No new imports or method definitions are required.

---

To resolve this issue, add an explicit permissions block to the workflow YAML. This can be added at the root of the workflow (above or below the name: and on: keys, but before jobs:) to serve as the default for all jobs. Since the workflow only needs to check out code and upload coverage reports, the minimal permission needed is typically contents: read. If the codecov/codecov-action@v4 step or any other step requires additional permissions, these can be expanded appropriately. However, in almost all CI testing/coverage/linting jobs, contents: read suffices.
Change needed: Insert at the root of .github/workflows/admin-tests.yml (after name: and before or after on:), the following:

permissions:
  contents: read

No new methods, imports, or definitions are necessary—just this addition to the workflow file.

---

To fix the problem, you should add a permissions block at the top level of the workflow file, immediately following the workflow name and before the on: trigger section, to set minimal required permissions for all jobs. Based on the observed steps, none of the jobs require write access—they only check out code, run tests, generate and upload reports. The minimal necessary permission for public repositories (and most CI workflows) is usually contents: read. Unless there is a known need in these jobs for additional scopes, you can confidently start with this restrictive setting. If you later need specific write access (for example, uploading artifacts to releases), expand only as needed.

Where to change:
Edit .github/workflows/admin-tests.yml by inserting the following block after name: Admin Dashboard Tests:

permissions:
  contents: read

Additional info:
No other code, imports, or definitions are required.

---

The best way to fix this problem is to explicitly add a permissions block at the root of the workflow file, setting the default required permission for all jobs to contents: read. This is the minimal permission required for the code checkout step (actions/checkout), and is a safe minimal base since none of the jobs appear to require write permissions (e.g., releasing, pushing code, or making pull requests). If uploading coverage needed write access to pull requests, additional permissions could be granted accordingly, but the best starting point is the recommended contents: read.
Change required:

• Insert the following under the first line (name: Admin Dashboard Tests) as a new second line:

  permissions:
    contents: read

---