Skip to content

5.3.1#270

Merged
HowardBraham merged 2 commits intomainfrom
release/5.4.0
Feb 2, 2026
Merged

5.3.1#270
HowardBraham merged 2 commits intomainfrom
release/5.4.0

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Feb 2, 2026

This is the release candidate for version 5.3.1.


Note

Low Risk
Low risk release bookkeeping only: updates package version and changelog entries/links without changing runtime code.

Overview
Prepares the 5.3.1 release by bumping package.json version from 5.3.0 to 5.3.1.

Updates CHANGELOG.md with a new 5.3.1 Fixed entry (Windows CRLF validation issue) and adjusts the compare links to point Unreleased at v5.3.1...HEAD.

Written by Cursor Bugbot for commit 2f2f118. This will update automatically on new commits. Configure here.

@HowardBraham HowardBraham marked this pull request as ready for review February 2, 2026 17:17
@HowardBraham HowardBraham requested a review from a team as a code owner February 2, 2026 17:17
@HowardBraham HowardBraham requested a review from mcmire February 2, 2026 17:17
@HowardBraham HowardBraham enabled auto-merge (squash) February 2, 2026 17:19
HowardBraham
HowardBraham previously approved these changes Feb 2, 2026
CHANGELOG.md Outdated
Comment on lines +15 to +18

### Added

- Added preview builds ([#268](https://github.com/MetaMask/auto-changelog/pull/268))
Copy link
Contributor

Choose a reason for hiding this comment

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

Usually we only include changes to the changelog that affect the publicly usable parts of the package, such as the CLI or API. Since this is a developer-only change, should we omit it?

Suggested change
### Added
- Added preview builds ([#268](https://github.com/MetaMask/auto-changelog/pull/268))

Given this, should we set the version to 5.3.1 rather than 5.4.0?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm... I just realized that if we want change the version we may have to make a new release PR. I think the release workflow looks at the name of the branch to know what the new version should be rather than package.json.

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh, sure, what's the best way to change the version? Does it have to be a new PR?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think so, unfortunately :(

@HowardBraham HowardBraham changed the title 5.4.0 5.3.1 Feb 2, 2026
Copy link
Contributor

@mcmire mcmire left a comment

Choose a reason for hiding this comment

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

LGTM.

@HowardBraham HowardBraham merged commit 9c9aff3 into main Feb 2, 2026
26 checks passed
@HowardBraham HowardBraham deleted the release/5.4.0 branch February 2, 2026 18:14
mcmire added a commit that referenced this pull request Feb 2, 2026
This reverts commit 9c9aff3. The
subject of this commit indicates that 5.4.0 is being released, when it
was actually 5.3.1.
mcmire added a commit that referenced this pull request Feb 3, 2026
This reverts commit 9c9aff3. The
subject of this commit indicates that 5.4.0 is being released, when it
was actually 5.3.1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants