Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Match what the standard setup will be starting with 2023.2. There are no changes needed to the code so we might as well start doing this now.
What has been done to verify that this works as intended?
Nothing, CI should be enough.
Why is this the best possible solution? Were any other approaches considered?
We could wait until we're ready to release backend but I don't see any advantage in that. I used 14.6 which is the latest available from CircleCI. This matches our recommendations in docs.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
None, this is CI only.
Does this change require updates to the API documentation? If so, please update docs/api.md as part of this PR.
No.
Before submitting this PR, please make sure you have:
make test-full
and confirmed all checks still pass OR confirm CircleCI build passes