fix(PL-6101): use upstream TriPSs/conventional-changelog-action#274
Merged
nwaller-nesto merged 1 commit intoJun 8, 2026
Merged
Conversation
Switch from nestoca fork to upstream TriPSs/conventional-changelog-action pinned to commit SHA for supply-chain safety. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
nwaller-nesto
requested review from
alexstojda,
ayahajar,
davidmdm,
j-martin,
riclima and
silphid
as code owners
silphid
approved these changes
Jun 8, 2026
nwaller-nesto
deleted the
fix/PL-6101-upstream-conventional-changelog-action
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Switch from
nestoca/conventional-changelog-actiontoTriPSs/conventional-changelog-action@3c4970b6 # releases/v5(upstream).Why
Maintaining the nestoca fork is unnecessary overhead. Pinning an action to a specific upstream commit SHA gives the same supply-chain guarantee as maintaining a fork — making the fork unnecessary. We're dropping the fork in favour of pinning directly to the upstream release branch.
References
Note
Low Risk
Single CI dependency swap with the same step configuration; release behavior could differ only if v5 outputs differ from the fork, but scope is limited to changelog generation on master.
Overview
The publish job in
build-test.yamlnow runs TriPSs/conventional-changelog-action at commit3c4970b6(releases/v5) instead of the nestoca fork that pointed atreleases/v4.All with: inputs for the “Generate changelog and tag release” step are unchanged; only the action source and pinned SHA differ.
Reviewed by Cursor Bugbot for commit f5cfac6. Bugbot is set up for automated code reviews on this repo. Configure here.