fix(ci): compare release changelog against previous streamkit tag only #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the release changelog to compare against the previous streamkit release tag instead of any tag (including plugin tags). The
git describecommand in the changelog generation step now uses--match 'v[0-9]*'to only consider streamkit version tags (e.g.,v0.2.0) and skip plugin tags (e.g.,plugin-helsinki-v0.1.0).Root cause:
git describe --tags --abbrev=0 HEAD^finds the nearest reachable tag of any kind. Since plugin tags likeplugin-helsinki-v0.1.0were closer tov0.3.0-devthanv0.2.0, the changelog was generated against the wrong base — as seen on the v0.3.0-dev release page.Review & Testing Checklist for Human
v[0-9]*correctly matches all current and expected future streamkit version tags (e.g.,v0.2.0,v0.3.0-dev,v1.0.0-rc1) while excluding all plugin tags (plugin-*-v*)git describe --tags --abbrev=0 --match 'v[0-9]*' <commit>^at a commit where plugin tags sit between two streamkit release tagsNotes