v6.1.0#11025
Conversation
/me ducks (I actually have no idea what happened) |
| Umar Hansa <umar.hansa@gmail.com> | ||
|
|
||
| ## Notable Changes | ||
| ~~ TODO: Move notable changes here ~~ |
There was a problem hiding this comment.
not sure we have major ones, 6.2 will be juicy with 'em though :)
There was a problem hiding this comment.
I added two things here.
| Loftie Ellis <lpellis@gmail.com> | ||
| Marvin Frachet <marvin.frachet@gmail.com> | ||
| Matt Hobbs <matthew.hobbs@digital.cabinet-office.gov.uk> | ||
| Peter Marshall <p.s.marshall0@gmail.com> | ||
| Umar Hansa <umar.hansa@gmail.com> |
There was a problem hiding this comment.
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?
| Loftie Ellis <lpellis@gmail.com> | |
| Marvin Frachet <marvin.frachet@gmail.com> | |
| Matt Hobbs <matthew.hobbs@digital.cabinet-office.gov.uk> | |
| Peter Marshall <p.s.marshall0@gmail.com> | |
| Umar Hansa <umar.hansa@gmail.com> | |
| Loftie Ellis @lpellis | |
| Marvin Frachet @mfrachet | |
| Matt Hobbs @Nooshu | |
| Peter Marshall @psmarshall |
There was a problem hiding this comment.
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 chrome-launcher@0.13.3 ([#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)) |
There was a problem hiding this comment.
should these two be in Tests?
|
|
||
| ~~ 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). |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
not very automatable
|
|
||
| ## I18n | ||
|
|
||
| * adjust LCP element description ([#11018](https://github.com/GoogleChrome/lighthouse/pull/11018)) |
There was a problem hiding this comment.
cc @exterkamp fyi I think we want to keep i18n: to just things that affect the i18n system, not that touch any string
There was a problem hiding this comment.
Makes sense. Been awhile since I've used these tags 😟
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
|
|
||
| ~~ 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). |
There was a problem hiding this comment.
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
Co-authored-by: Brendan Kenny <bckenny@gmail.com>
Co-authored-by: Brendan Kenny <bckenny@gmail.com>
Co-authored-by: Brendan Kenny <bckenny@gmail.com>
| Loftie Ellis @lpellis | ||
| Marvin Frachet @mfrachet | ||
| Matt Hobbs @Nooshu | ||
| Peter Marshall @psmarshall |
There was a problem hiding this comment.
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"> |
There was a problem hiding this comment.
should be with the second bullet point?
There was a problem hiding this comment.
I thought it was a nice showcase of both at the same time :)
There was a problem hiding this comment.
it shows both things tho
There was a problem hiding this comment.
I thought it was a nice showcase of both at the same time :)
it shows both things tho
oh, haha, fair enough
Co-authored-by: Brendan Kenny <bckenny@gmail.com>
Co-authored-by: Brendan Kenny <bckenny@gmail.com>
Co-authored-by: Brendan Kenny <bckenny@gmail.com>

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-colorand filtering based ontag: .... but the way it does this misses thev6.0.0for some reason, so I was given a changelong ofv5.6.0...6.1.0.it basically does this
notice there's no v6.0.0
the v6.0.0 tag points to

c61e0d662c0f1156e3d174529bcf7e29e1b26566, which if you log it withgit log c61e0d6...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)@brendankenny @paulirish wat did ya'll do? 😢
once I figured out the issue I just manually push
v6.0.0to the tags innode_modules/git-semver-tags/index.jsand commented out some lines inprepare-commit.sh.