[release] Release from this repo is quite manual

[prabhu]

We need to bump up the version in a couple of files and manually create a tag for every depscan release. Probably need an automated way of releasing things.

[saketjajoo]

Just a thought - If a PR is created for every new release with the body/title of the PR having a tag name (say vX.Y.Z) we can use GitHub Actions to create a release (modifying the necessary files with the updated version/tag as a part of the action) once the PR gets merged. That action can also create a new tag before creating/publishing a release.

Note: It seems that creating a release cannot be fully automated currently because they require a tag to be created (either manually or via a script [perhaps GitHub Actions - which will require a trigger (say a PR)]. If we have a PR for creating a release, it can take care of creating a new tag and then a new release.

[prabhu]

@saketjajoo, good thinking. perhaps we clone this repo and use git tag from an action in depscan?

[saketjajoo]

@saketjajoo, good thinking. perhaps we clone this repo and use git tag from an action in depscan?

This may require adding a PAT in both the repos (depscan and depscan-bin) as the default GITHUB_TOKEN may not be privileged enough to create a tag from the depscan repo to the depscan-bin repo.

[prabhu]

Let's revisit this later.