Potential fix for code scanning alert no. 3: Workflow does not contain permissions

[bdk38]

Potential fix for https://github.com/bdk38/HellPot/security/code-scanning/3

To fix the problem, add an explicit permissions block granting the least privileges needed for this workflow. Because there is only a single job and all steps are in that job, the simplest and clearest fix is to add permissions under jobs.release so it applies specifically to this job. The steps use actions/checkout (needs contents: read), wangyoucao577/go-release-action to build and create GitHub releases (needs contents: write to upload release assets and possibly manage releases), and Docker login/build/push actions (which interact with Docker Hub and GHCR using secrets and GITHUB_TOKEN for registry auth, which typically maps to packages: write in GitHub’s permission model).

The best minimal permissions set that preserves existing functionality is therefore:

• contents: write – needed for creating/updating releases and uploading assets.
• packages: write – needed to push images to ghcr.io.

No other scopes (like actions, pull-requests, issues, etc.) appear necessary from the provided snippet. Concretely, in .github/workflows/release-command.yml, under jobs:, inside the release: job and at the same indentation level as runs-on:, add:

    permissions:
      contents: write
      packages: write

No additional methods, imports, or other definitions are needed since this is purely a workflow configuration change.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.