Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v6.1.0 #11025

Merged
merged 12 commits into from
Jun 25, 2020
Merged

v6.1.0 #11025

merged 12 commits into from
Jun 25, 2020

Conversation

connorjclark
Copy link
Collaborator

@connorjclark connorjclark commented Jun 25, 2020

I got to this later than I planned–just tossing this up for now and will give a first pass in the morning.

meta

generating this changelog was a real hassle and I'm not certain why.

the changelog generator collects a list of git tags by calling git log --decorate --no-color and filtering based on tag: .... but the way it does this misses the v6.0.0 for some reason, so I was given a changelong of v5.6.0...6.1.0.

it basically does this

git log --decorate --no-color | grep tag:                                                                       SIGPIPE(13) ↵  10993  22:41:50
commit 468c10bb9df7ded215b7a3c47e23f48c1af656f7 (tag: v6.0.0-beta.0)
commit 848b54397bd062f83d00ac8a87608df8011cf8f1 (tag: v5.6.0)
commit 4e15a56171be0c622186b3ce58cf1fbce000e9e5 (tag: v5.5.0)
commit 364ca5919296235dfcc00f20f8ccca9ec33807c0 (tag: v5.4.0)
commit f170bed81b1e102ab3655529dd70e07dd28944b3 (tag: v5.3.0)
commit ba1e1591dd83fe411f058df31a994df76796f646 (tag: v5.2.0)
commit cab03b4b5afa52ccd27c8fcb1582d1ba0a0e1410 (tag: v5.1.0)
...

notice there's no v6.0.0

the v6.0.0 tag points to c61e0d662c0f1156e3d174529bcf7e29e1b26566, which if you log it with git log c61e0d6...
image

what teh eff, there's the tag...

the tag doesn't show up (different commit too..) if you do just git log --decorate (Thus why it didn't get picked up by changelog generator)
image

@brendankenny @paulirish wat did ya'll do? 😢

once I figured out the issue I just manually push v6.0.0 to the tags in node_modules/git-semver-tags/index.js and commented out some lines in prepare-commit.sh.

@connorjclark connorjclark requested a review from a team as a code owner June 25, 2020 05:49
@connorjclark connorjclark requested review from patrickhulce and removed request for a team June 25, 2020 05:49
@brendankenny
Copy link
Member

brendankenny commented Jun 25, 2020

@brendankenny @paulirish wat did ya'll do? 😢

git show v6.0.0\ntag v6.0.0\nTagger: Paul Irish <commits@paul.irish>

/me ducks
😁

(I actually have no idea what happened)

changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
docs/recipes/integration-test/package.json Outdated Show resolved Hide resolved
changelog.md Outdated
Umar Hansa <[email protected]>

## Notable Changes
~~ TODO: Move notable changes here ~~
Copy link
Collaborator

Choose a reason for hiding this comment

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

not sure we have major ones, 6.2 will be juicy with 'em though :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I added two things here.

changelog.md Outdated
Comment on lines 10 to 14
Loftie Ellis <[email protected]>
Marvin Frachet <[email protected]>
Matt Hobbs <[email protected]>
Peter Marshall <[email protected]>
Umar Hansa <[email protected]>
Copy link
Collaborator

Choose a reason for hiding this comment

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

we should really try to map these back to github login, I guess we could replace it with a github API lookup on the commit itself?

I can look into that

for this release just manual?

Suggested change
Loftie Ellis <[email protected]>
Marvin Frachet <[email protected]>
Matt Hobbs <[email protected]>
Peter Marshall <[email protected]>
Umar Hansa <[email protected]>
Loftie Ellis @lpellis
Marvin Frachet @mfrachet
Matt Hobbs @Nooshu
Peter Marshall @psmarshall

Copy link
Collaborator Author

@connorjclark connorjclark Jun 25, 2020

Choose a reason for hiding this comment

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

yes please and ty so much for doing this bit for me :)

ref #9857

* axe-core: upgrade to 3.5.5 ([#10986](https://github.com/GoogleChrome/lighthouse/pull/10986))
* upgrade [email protected] ([#10911](https://github.com/GoogleChrome/lighthouse/pull/10911))
* snyk: update snyk snapshot ([#10840](https://github.com/GoogleChrome/lighthouse/pull/10840), [#10940](https://github.com/GoogleChrome/lighthouse/pull/10940), [#10980](https://github.com/GoogleChrome/lighthouse/pull/10980), [#11010](https://github.com/GoogleChrome/lighthouse/pull/11010))
* remove bundlesize ([#10999](https://github.com/GoogleChrome/lighthouse/pull/10999))
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

should these two be in Tests?

@@ -13,4 +13,4 @@


~~ TODO: https://chromiumdash.appspot.com/schedule ~~
We expect this release to ship in the DevTools of Chrome XX.
We expect this release to ship in the DevTools of [Chrome XX](https://chromiumdash.appspot.com/schedule).
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yea?

Copy link
Member

Choose a reason for hiding this comment

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

any chance there's a permalink to a version? I couldn't find one easily. It's a shame the link is mostly useless after 18 weeks

Copy link
Collaborator Author

Choose a reason for hiding this comment

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


## I18n

* adjust LCP element description ([#11018](https://github.com/GoogleChrome/lighthouse/pull/11018))
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

report??

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

cc @exterkamp fyi I think we want to keep i18n: to just things that affect the i18n system, not that touch any string

Copy link
Member

Choose a reason for hiding this comment

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

Makes sense. Been awhile since I've used these tags 😟

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think that was actually my bad. I think it was core(i18n): and I was like "don't we have an i18n separate scope? and changed it before merge".

I kinda stand by the fact that this was an adjustment raised by i18n clarity purposes, but agreed generally strings shouldn't be i18n scope. Maybe core(lcp): adjust element description would've been best?

report feels weird since it has nothing to do with HTML report, it applies to all LHR uses

Copy link
Member

Choose a reason for hiding this comment

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

report feels weird since it has nothing to do with HTML report, it applies to all LHR uses

yeah, it feels a little weird but I usually put these in core

@@ -13,4 +13,4 @@


~~ TODO: https://chromiumdash.appspot.com/schedule ~~
We expect this release to ship in the DevTools of Chrome XX.
We expect this release to ship in the DevTools of [Chrome XX](https://chromiumdash.appspot.com/schedule).
Copy link
Member

Choose a reason for hiding this comment

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

any chance there's a permalink to a version? I couldn't find one easily. It's a shame the link is mostly useless after 18 weeks

changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
Co-authored-by: Brendan Kenny <[email protected]>
Co-authored-by: Brendan Kenny <[email protected]>
changelog.md Outdated
Loftie Ellis @lpellis
Marvin Frachet @mfrachet
Matt Hobbs @Nooshu
Peter Marshall @psmarshall
Copy link
Member

Choose a reason for hiding this comment

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

formatting on these doesn't look so great

* If a page has publicly-accessible JavaScript source maps, Lighthouse will collect them to enhance the `unused-javascript` audit. In future versions of Lighthouse, source maps will be used for entirely new audits [#10990](https://github.com/GoogleChrome/lighthouse/pull/10990)
* The report now uses `KiB` instead of `KB`. This is simply a label change; the value was and still is equal to `1024 bytes` [#10870](https://github.com/GoogleChrome/lighthouse/pull/10870)

<img src="https://i.imgur.com/1gSdPw5.png" alt="Unused JavaScript with source maps" width="800px">
Copy link
Member

Choose a reason for hiding this comment

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

should be with the second bullet point?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I thought it was a nice showcase of both at the same time :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it shows both things tho

Copy link
Member

Choose a reason for hiding this comment

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

I thought it was a nice showcase of both at the same time :)

it shows both things tho

oh, haha, fair enough

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

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

otherwise LGTM2!

changelog.md Outdated Show resolved Hide resolved
changelog.md Outdated Show resolved Hide resolved
@connorjclark connorjclark merged commit 4c4b628 into master Jun 25, 2020
@connorjclark connorjclark deleted the bump_6.1.0 branch June 25, 2020 20:27
gMakunde pushed a commit to gMakunde/lighthouse that referenced this pull request Jul 6, 2020
Co-authored-by: Brendan Kenny <[email protected]>
gMakunde pushed a commit to gMakunde/lighthouse that referenced this pull request Aug 28, 2020
Co-authored-by: Brendan Kenny <[email protected]>
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.

6 participants