Skip to content

Commit 9ae6edc

Browse files
gabalafoutrallard
andauthored
Set treosh/lighthouse-ci-action to 12.1.0 (#2223)
In the past couple of the weeks the performance score for the Lighthouse audit dropped below 0.8 and started making CI fail. This change in the CI result was surprising because there have been very few commits to main since 3e74810, and none that should have affected the Lighthouse performance score. Looking for a culprit, I noticed that the `v12` tag for `treosh/lighthouse-ci-action` was updated 2 weeks ago, pointing the tag from Lighthouse version 12.1.0 to 12.6.0, which one can see in the [treosh/lighthouse-ci-action releases](https://github.com/treosh/lighthouse-ci-action/tags). There are a good number of changes between those two versions, as shown in the [Lighthouse releases].(https://github.com/GoogleChrome/lighthouse/releases), but I haven't yet identified which of them may have affected the score. But before investigating too deeply, the easiest thing we can do to test this hypothesis is to downgrade the version of the GitHub action, and see if that fixes CI. --------- Co-authored-by: Tania Allard <[email protected]>
1 parent 0919145 commit 9ae6edc

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

.github/workflows/docs.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,8 @@ jobs:
110110
DOCS_DIR: "audit"
111111

112112
- name: "Audit with Lighthouse 🔦"
113-
uses: treosh/lighthouse-ci-action@v12
113+
# pin to Lighthouse version 12.1.0
114+
uses: treosh/lighthouse-ci-action@2f8dda6cf4de7d73b29853c3f29e73a01e297bd8
114115
with:
115116
configPath: ".github/workflows/lighthouserc.json"
116117
temporaryPublicStorage: true

0 commit comments

Comments
 (0)