bump: fix the goreleaser release cycle & Dependabot

[amands98]

This PR fixes the failing workflow

This PR suggests tagging v0.1.0-beta.1 and proceeding with the release.

Updated goreleaser configuration, @Vad1mo . Add GH_TOKEN secret with repo scope, write:packages.
Also I included a dependabot, to automate dependency updates.

After merging, let's release the packages on Homebrew, Winget, Nix, and Snap.

[JaeAeich]

It would also make a lot of sense IMO to make a install script that Unix users can pipe into bash/zsh to make the release form source and configure the binaries into the right directories, something like ~/usr/local/bin .

[bishal7679]

It would also make a lot of sense IMO to make a install script that Unix users can pipe into bash/zsh to make the release form source and configure the binaries into the right directories, something like ~/usr/local/bin .

Yes! #18 doing the same thing but need to clone the repository.

[Vad1mo]

I need to check that @OrlinVasilev, I don't have the owner permission set for the org to request such a token
.
.

[OrlinVasilev]

will take care of that :)

[OrlinVasilev]

not sure why are you renaming the token to GH_TOKEN ? what's the idea behind it that comes by default

[OrlinVasilev]

@amands98 check this run after the fix https://github.com/goharbor/harbor-cli/actions/runs/7905056008/job/21984205486

[bishal7679]

not sure why are you renaming the token to GH_TOKEN ? what's the idea behind it that comes by default

It automatically fetches if we specify as GITHUB_TOKEN otherwise for different naming we need to set that as repo secret var.

[OrlinVasilev]

@bishal7679 exactly :) we have it working with the default token no need for additional one IMO ?

[amands98]

just following the naming rules.
https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#naming-your-secrets

[Vad1mo]

just following the naming rules. https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#naming-your-secrets

Makes sense if you are creating your own secret, however we are reusing the exising one here.

[Vad1mo]

@amands98 Can you address my comment?

[amands98]

Sure, let's use the default GITHUB_TOKEN with the required scopes (repo, write:packages). After that, we can merge and re-run the workflow to ensure the harbor-cli binaries are generated effectively.