Setting Prettier's version number on our GitHub Action and package.json. This will allow us to keep the checks synced. If we use a mismatched version, there is potential for formatting errors that are also mismatched. For example, 2.3.0 has more checks than 2.2.1, so the 2.3.0 prettier --check command can fail while 2.2.1 may pass.
The index.js file in this Pull Request was caught in the example situation.
Note the failing linter (pull_request_target) Action - this is failing because the master branch has the violation. This should go away when this PR is merged.
Setting Prettier's version number on our GitHub Action and package.json. This will allow us to keep the checks synced. If we use a mismatched version, there is potential for formatting errors that are also mismatched. For example, 2.3.0 has more checks than 2.2.1, so the 2.3.0 prettier --check command can fail while 2.2.1 may pass.
The index.js file in this Pull Request was caught in the example situation.