Added caching actions

[DomPeliniAerospike]

No description provided.

To fix the problem, we need to add an explicit permissions: block to the workflow file, specifying the minimal necessary permissions for this workflow and its jobs. The recommended approach is to set permissions: at the workflow root, which will apply to all jobs unless overridden, for maximal coverage. For most workflows, the minimum safe default is contents: read, unless more write permissions are specifically needed for steps in the jobs. Since the jobs here only call child workflows, and we don't see any inline write actions, it's safest to set contents: read. If one or more jobs require elevated permissions, you can override at the job level.

Edit .github/workflows/master-workflow.yml and insert the following block at the top level, immediately after name: and before on::

permissions:
  contents: read

No imports or method changes are needed.

---

To fix this security issue, explicitly set a permissions: block at the root level of the workflow in .github/workflows/master-workflow.yml. This will ensure GITHUB_TOKEN is limited to only what the jobs require and defaults to "read-only" for contents, unless specific jobs need extra permissions.

• Insert a permissions: block immediately after the name: and before on: (usually line 2 or 3).
• For most CI/CD workflows, the typical minimal block is:

  permissions:
    contents: read

  If any job requires write access to e.g. pull requests, issues, or packages, those can be added as needed, but in the absence of such needs in the shown file, the above is a safe minimal starting point.
• No other code changes or imports are needed, just the insertion of this block.

---

To fix this issue, explicitly declare a permissions block at the root level of the workflow file. This will ensure all jobs within the workflow inherit safe, least-privilege permissions for the GITHUB_TOKEN unless overridden by individual jobs. The most restrictive baseline for most workflows is contents: read; if any jobs require specific write access (e.g., to create pull requests or modify issues), those types should be granted explicit permission. Based on the provided jobs (which mostly publish packages and upload artifacts, but do not appear to write to issues or PRs), the minimal starting point would be:

permissions:
  contents: read

You should add the following block just below the workflow name: and above the on: section for clarity and consistency. No imports, methods, or variable definitions are required.