Skip to content

Add categories to each changelog release#10837

Merged
Gudahtt merged 3 commits intodevelopfrom
add-changelog-sections
Apr 7, 2021
Merged

Add categories to each changelog release#10837
Gudahtt merged 3 commits intodevelopfrom
add-changelog-sections

Conversation

@Gudahtt
Copy link
Copy Markdown
Member

@Gudahtt Gudahtt commented Apr 7, 2021

Each changelog release now has category headers. The standard "keep a changelog" categories are used, along with the addition of "Uncategorized" for any changes that have not yet been categorized.

The changelog script has been updated to add this "Uncategorized" header if it isn't already present, and to place any new commits under this header.

The changelog has been updated to property categorize each change in recent releases, and to place changes in older releases under the header "Uncategorized".

Relates to #10752

Manual testing steps:

For development changelog updates:

  • Run yarn update-changelog
  • See that it places changelog entries under 'Unreleased`, under the "Uncategorized" header

For RC changelog updates with existing release header:

  • Bump the version in app/manifest/_base.json, to simulate an RC-like environment
  • Add a new release header to the changelog for the new version
  • Run yarn update-changelog
  • See that it places changelog entries under the new release header under the "Uncategorized" category

For updates without a release header:

  • Bump the version in app/manifest/_base.json, to simulate an RC-like environment
  • Run yarn update-changelog
  • See that it places changelog entries under the newly added release header under the "Uncategorized" category

Each changelog release now has category headers. The standard "keep a
changelog" [1] categories are used, along with the addition of
"Uncategorized" for any changes that have not yet been categorized.

The changelog script has been updated to add this "Uncategorized"
header if it isn't already present, and to place any new commits under
this header.

The changelog has been updated to property categorize each change in
recent releases, and to place changes in older releases under the
header "Uncategorized".

[1]: https://keepachangelog.com/en/1.0.0/
@Gudahtt Gudahtt requested review from a team and kumavis as code owners April 7, 2021 01:25
@Gudahtt Gudahtt requested a review from darkwing April 7, 2021 01:25
const changelog = await fs.readFile(changelogFilename, { encoding: 'utf8' });
const changelogLines = changelog.split('\n');

const prNumbersWithChangelogEntries = [];
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This was moved earlier in the script to allow the early exit on line 99, to ensure we don't add the 'Uncategorized' header to the "Unreleased" section if there are no changes.

As a bonus, it now avoids creating a new release header if there are no commits as well! Though that shouldn't happen generally.

@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [1f60090]
Page Load Metrics (610 ± 61 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint468061105
domContentLoaded39977660912661
load40177761012661
domInteractive39977660912661

A few releases were missing the 'Uncategorized' header due to
inconsistencies in formatting. The formatting for each release has
been made consistent, and any missing 'Uncategorized' headers have
been added.
- Add Parity compatibility, fixing Geth dependency issues.
- Add a link to the transaction in history that goes to https://metamask.github.io/eth-tx-viz
too help visualize transactions and to where they are going.
- Add a link to the transaction in history that goes to https://metamask.github.io/eth-tx-viz to help visualize transactions and to where they are going.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I moved this onto one line to make the formatting more consistent and easier to parse. I also fixed a typo here (too => to).

- Fixed bug where if you send a transaction from within MetaMask extension the
popup notification opens up.
### Uncategorized
- Fixed bug where if you send a transaction from within MetaMask extension the popup notification opens up.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This was moved onto one line as well.


Made seed word restoring BIP44 compatible.
### Uncategorized
- Made seed word restoring BIP44 compatible.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

These older releases didn't have a - in front of their changes. I've added it to make them consistent with the others.

@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [8764b04]
Page Load Metrics (622 ± 58 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint47815984
domContentLoaded37278862112058
load37479062212058
domInteractive37178862112058

brad-decker
brad-decker previously approved these changes Apr 7, 2021
Copy link
Copy Markdown
Contributor

@brad-decker brad-decker left a comment

Choose a reason for hiding this comment

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

This LGTM though I'd like some clarification on how the various categories are determined. What differentiates changed/added vs fixed?

@Gudahtt
Copy link
Copy Markdown
Member Author

Gudahtt commented Apr 7, 2021

The keep a changelog spec describes the categories as follows:

  • Added for new features.
  • Changed for changes in existing functionality.
  • Deprecated for soon-to-be removed features.
  • Removed for now removed features.
  • Fixed for any bug fixes.
  • Security in case of vulnerabilities.

Sometimes the line between what counts as a change to an existing feature v.s a new feature v.s a bug fix is blurry. But that's fine.We can pick whichever we think would be most useful for readers.

The "Add setting to hide zero balance tokens" changelog entry was
accidentally moved from v9.2.0 to v9.2.1. It has been moved back.
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [a7e6e05]
Page Load Metrics (590 ± 41 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint44705773
domContentLoaded3477095898541
load3487105908541
domInteractive3477095888541

@Gudahtt Gudahtt merged commit 1c5dcd6 into develop Apr 7, 2021
@Gudahtt Gudahtt deleted the add-changelog-sections branch April 7, 2021 15:42
@github-actions github-actions bot locked and limited conversation to collaborators Apr 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants