Skip to content

Conversation

@Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Mar 30, 2022

Explanation

When we want to rollback a release on Chrome, sometimes we use the fourth part of the version for the rollback release. This is because the Chrome web stores does not directly allow rolling back, but instead requires us to re-submit the release we want to roll back to with a higher version number.

The manifest version parsing now allows for a fourth version part.

The comments have also been updated to be more descriptive, and to fix a minor inaccuracy.

Manual testing steps

  • Try adding a fourth part to the version number in package.json (e.g. "v10.12.2.1").
  • Ensure that the extension can connect to dapps, that there are no background console errors, and that the "About" page renders the version properly.

@Gudahtt Gudahtt marked this pull request as ready for review March 31, 2022 00:07
@Gudahtt Gudahtt requested a review from a team as a code owner March 31, 2022 00:07
@Gudahtt Gudahtt requested a review from NiranjanaBinoy March 31, 2022 00:07
When we want to rollback a release on Chrome, sometimes we use the
fourth part of the version for the rollback release. This is because
the Chrome web stores does not directly allow rolling back, but instead
requires us to re-submit the release we want to roll back to with a
higher version number.

The manifest version parsing now allows for a fourth version part.

The comments have also been updated to be more descriptive, and to fix
a minor inaccuracy.
@Gudahtt Gudahtt force-pushed the update-version-parsing-to-allow-rollback-release branch from 555bc31 to 7b66187 Compare March 31, 2022 00:10
@metamaskbot
Copy link
Collaborator

Builds ready [7b66187]
Page Load Metrics (1324 ± 62 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint711268160259124
domContentLoaded11651589132113063
load11741589132412862
domInteractive11651588132113063

ryanml
ryanml previously approved these changes Mar 31, 2022
Copy link
Contributor

@darkwing darkwing left a comment

Choose a reason for hiding this comment

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

Tiniest, most infuriating nit ever.

Gudahtt and others added 2 commits April 4, 2022 12:46
Co-authored-by: David Walsh <davidwalsh83@gmail.com>
@metamaskbot
Copy link
Collaborator

Builds ready [2ac8d3e]
Page Load Metrics (1255 ± 37 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint8014792157
domContentLoaded1170140412425627
load1183152712557637
domInteractive1170140412425627

Copy link
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.

LGTM. Tested locally as well.

@metamaskbot
Copy link
Collaborator

Builds ready [e4bc689]
Page Load Metrics (1675 ± 30 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint7911396105
domContentLoaded1537178916546431
load1552180416756230
domInteractive1537178916546431

@Gudahtt Gudahtt merged commit 23e3f52 into develop May 3, 2022
@Gudahtt Gudahtt deleted the update-version-parsing-to-allow-rollback-release branch May 3, 2022 16:48
@github-actions github-actions bot locked and limited conversation to collaborators May 3, 2022
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.

6 participants