Skip to content

Conversation

@kanthesha
Copy link
Contributor

Explanation

Currently, the create-release-pr action is terminated with an error message ("updateChangelog" returned an empty value for package ...) and the release candidate is not created if the updateChangelog call does not return any new entries, but there are unreleased changes.

The error should be triggered only if both of the following are true:

  • updateChangelog returns a null value.
  • There are no unreleased changes present in the changelog

References

@kanthesha kanthesha marked this pull request as ready for review August 20, 2024 12:52
@kanthesha kanthesha requested a review from a team as a code owner August 20, 2024 12:52
mikesposito
mikesposito previously approved these changes Aug 20, 2024
Copy link
Member

@mikesposito mikesposito left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@kanthesha kanthesha merged commit d2cc9bb into main Aug 20, 2024
@kanthesha kanthesha deleted the fix/rc-unreleased-changes branch August 20, 2024 15:24
Gudahtt added a commit to MetaMask/ppom-validator that referenced this pull request Sep 5, 2025
Update the action `action-create-release-pr` to v3.0.1, which includes
a bug fix impacting the next release (MetaMask/action-create-release-pr#139)

The v2 updated included no relevant breaking changes (just a Node.js
minimum version bump), but the v3 update changed the formatting of the
changelog to use Prettier. All changelog commands have been updated to
use Prettier formatting, and the changelog has been reformatted.

Changelog: https://github.com/MetaMask/action-create-release-pr/blob/main/CHANGELOG.md#301

I didn't update as far as v4 of this action because that would have
required further changes (namely the update to Prettier v3).
Gudahtt added a commit to MetaMask/ppom-validator that referenced this pull request Sep 5, 2025
Update the action `action-create-release-pr` to v3.0.1, which includes
a bug fix impacting the next release (MetaMask/action-create-release-pr#139)

The v2 updated included no relevant breaking changes (just a Node.js
minimum version bump), but the v3 update changed the formatting of the
changelog to use Prettier. All changelog commands have been updated to
use Prettier formatting, and the changelog has been reformatted.

Changelog: https://github.com/MetaMask/action-create-release-pr/blob/main/CHANGELOG.md#301

I didn't update as far as v4 of this action because that would have
required further changes (namely the update to Prettier v3).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release candidate should be created even if updateChangelog does not return any new entries

3 participants