Summary

GitHub Action checks in the specifications have started failing to run js-yaml.

Motivation

Example failure:

if js-yaml server-selection/tests/in_window/equilibrium.yml > "$tmpfile"; then \
    mv "$tmpfile" server-selection/tests/in_window/equilibrium.json;            \
else                              \
    rm "$tmpfile";               \
    exit 1;                       \
fi
file:///opt/hostedtoolcache/node/12.22.12/x64/lib/node_modules/js-yaml/dist/js-yaml.mjs:9
		implicit: options.implicit ?? false,
		                            ^

Who is the affected end user?

DBX devs.

How does this affect the end user?

Adds development difficulty. Cannot validate spec changes against GitHub actions.

How likely is it that this problem or use case will occur?

Certain.

If the problem does occur, what are the consequences and how severe are they?

May cause further test issues to go unnoticed (e.g. failing to regenerate JSON files).

Is this issue urgent?

Somewhat? I expect the longer it fails, the more likely legitimate issue will go unnoticed.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.

Acceptance Criteria

• GitHub Actions pass on mongodb/specifications.