Skip to content

Commit 2a9aa28

Browse files
committed
ci(next-drupal): work-around for flakey code coverage reporting
Issue #740
1 parent 4bce663 commit 2a9aa28

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

.github/workflows/next-drupal.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,12 @@ jobs:
1414
with:
1515
ref: ${{github.event.pull_request.head.ref}}
1616
repository: ${{github.event.pull_request.head.repo.full_name}}
17+
# TODO: Work-around for failing code coverage.
18+
# https://github.com/chapter-three/next-drupal/issues/740
19+
- name: Use Node.js
20+
uses: actions/setup-node@v4
21+
with:
22+
node-version: '18.19.x'
1723
- name: Install packages
1824
run: yarn
1925
- name: Run tests

.nvmrc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,5 @@
1-
v18
1+
v18.19
2+
3+
# @TODO v18.20 and v20.10 and later have a bug that causes Jest code coverage to randomly fail. When the tracking bug is fixed, switch to the less-specific "v18" or "v20" version. See https://github.com/chapter-three/next-drupal/issues/740
4+
5+
# Note: This is a non-standard .nvmrc comment. Currently, nvm ignores all lines except the 1st line so we are hijacking this implementation detail to add comments to this file. See https://github.com/nvm-sh/nvm/pull/2288#issuecomment-1115079020

0 commit comments

Comments
 (0)