Maintain major/minor tags

[anton-yurchenko]

Hello @Templum,
This change will automatically maintain the vX and vX.X tags on every release. It should allow users to lock to a major version and update the workflows less frequently:

name: My Workflow
on: [push, pull_request]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: Templum/govulncheck-action@v1

In addition to that, the release flow will force a semantic version tag and not any tag that start with v letter.

[codecov-commenter]

Codecov Report

Patch and project coverage have no change.

Comparison is base (6dcc1fe) 98.02% compared to head (d7fecd4) 98.02%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #49   +/-   ##
=======================================
  Coverage   98.02%   98.02%           
=======================================
  Files           3        3           
  Lines         253      253           
=======================================
  Hits          248      248           
  Misses          4        4           
  Partials        1        1           

Flag	Coverage Δ
unit-tests	98.02% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Templum]

@anton-yurchenko thanks for your contribution, it makes sense to me. But I see an issue with your current setup.

It would also create multiple releases, where you probably just want that "one" release. And have those additional tags on the side. As the action will trigger the pipeline again on it's first run.

[anton-yurchenko]

The pipeline trigger is v[0-9]+.[0-9]+.[0-9]+ which must match only a full semantic version (without metadata, like -beta and such), for example v1.2.3.
This workflow execution will update v1 and v1.2 tags, which won't trigger the pipeline again as they aren't full semantic versions.

P.S: updated integrations pipeline to be triggered only once on fully qualified version tag

[anton-yurchenko]

@Templum can you please create v1 and v1.0 tags manually pointing to the v1.0.0 commit (6bb063b) so we can lock to the current major version?

[Templum]

@anton-yurchenko sure thing, will do it as soon as I find the time. I will notify you here, once it is done

[Templum]

@anton-yurchenko both are now available:

• https://github.com/Templum/govulncheck-action/releases/tag/v1
• https://github.com/Templum/govulncheck-action/releases/tag/v1.0