You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the changes in the tagging format was intentional, the GitHub workflow should be updated accordingly. If not, the tags for 2.2.7, 2.2.8, 2.3.0 should be fixed and the pinia@* format should be used for new releases.
Note that because of this, dependabot release notes are stuck at 2.2.6.
The text was updated successfully, but these errors were encountered:
ezio-melotti
changed the title
Missing GitHub releases due to incorrect Git tags format
Missing GitHub releases due to missing pinia@* tags
Dec 5, 2024
Steps to reproduce the bug
Go on https://github.com/vuejs/pinia/releases -- the last release is
2.2.6
.Go to https://github.com/vuejs/pinia/tags -- the last release is
2.3.0
.Expected behavior
2.2.7
,2.2.8
,2.3.0
should be listed in the releases page.Actual behavior
2.2.7
,2.2.8
,2.3.0
are missing from the releases page.Additional information
By looking at the workflow, it's triggered by commits tagged with
pinia@*
:pinia/.github/workflows/release-tag.yml
Lines 1 to 4 in 1d8f341
In https://github.com/vuejs/pinia/tags the releases up to
2.2.6
were tagged as e.g.[email protected]
and were triggering the workflow. The following releases are tagged as e.g.v2.2.7
.If the changes in the tagging format was intentional, the GitHub workflow should be updated accordingly. If not, the tags for
2.2.7
,2.2.8
,2.3.0
should be fixed and thepinia@*
format should be used for new releases.Note that because of this,
dependabot
release notes are stuck at2.2.6
.The text was updated successfully, but these errors were encountered: