fix(deps): update all dependencies to v16 and jest snaps j:cdx-227 #1390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
<!-- For Coveo Employees only. Fill this section.
CDX-XXX
-->
## Proposed changes
<!--
Explains what are you changing in the code and provide links to relevant
issues.
This doesn't need to be over-technical, a good summary of the issues
with good explanations of the decisions should be enough.
-->
## Breaking changes
<!--
Remove this section if the PR does not include any breaking change
If your changes includes some breaking changes in the code, thoroughly
explains:
- What are the breaking changes programmatically speaking.
- What is the impact on the end-user (e.g. user cannot do X anymore).
- What motivates those changes.
-->
## Testing
- [ ] Unit Tests:
<!-- Did you write unit tests for your feature? If not, explains why?
-->
- [ ] Functionnal Tests:
<!-- Did you write functionnal tests for your feature? If not, explains
why? -->
- [ ] Manual Tests:
<!-- How did you test your changeset? -->
<!-- For Coveo Employees only. Fill this section.
CDX-XXX
-->
## Proposed changes
<!--
Explains what are you changing in the code and provide links to relevant
issues.
This doesn't need to be over-technical, a good summary of the issues
with good explanations of the decisions should be enough.
-->
## Breaking changes
<!--
Remove this section if the PR does not include any breaking change
If your changes includes some breaking changes in the code, thoroughly
explains:
- What are the breaking changes programmatically speaking.
- What is the impact on the end-user (e.g. user cannot do X anymore).
- What motivates those changes.
-->
## Testing
- [ ] Unit Tests:
<!-- Did you write unit tests for your feature? If not, explains why?
-->
- [ ] Functionnal Tests:
<!-- Did you write functionnal tests for your feature? If not, explains
why? -->
- [ ] Manual Tests:
<!-- How did you test your changeset? -->
<!-- For Coveo Employees only. Fill this section.
CDX-XXX
-->
## Proposed changes
<!--
Explains what are you changing in the code and provide links to relevant
issues.
This doesn't need to be over-technical, a good summary of the issues
with good explanations of the decisions should be enough.
-->
## Breaking changes
<!--
Remove this section if the PR does not include any breaking change
If your changes includes some breaking changes in the code, thoroughly
explains:
- What are the breaking changes programmatically speaking.
- What is the impact on the end-user (e.g. user cannot do X anymore).
- What motivates those changes.
-->
## Testing
- [ ] Unit Tests:
<!-- Did you write unit tests for your feature? If not, explains why?
-->
- [ ] Functionnal Tests:
<!-- Did you write functionnal tests for your feature? If not, explains
why? -->
- [ ] Manual Tests:
<!-- How did you test your changeset? -->
<!-- For Coveo Employees only. Fill this section.
CDX-XXX
-->
## Proposed changes
<!--
Explains what are you changing in the code and provide links to relevant
issues.
This doesn't need to be over-technical, a good summary of the issues
with good explanations of the decisions should be enough.
-->
## Breaking changes
<!--
Remove this section if the PR does not include any breaking change
If your changes includes some breaking changes in the code, thoroughly
explains:
- What are the breaking changes programmatically speaking.
- What is the impact on the end-user (e.g. user cannot do X anymore).
- What motivates those changes.
-->
## Testing
- [ ] Unit Tests:
<!-- Did you write unit tests for your feature? If not, explains why?
-->
- [ ] Functionnal Tests:
<!-- Did you write functionnal tests for your feature? If not, explains
why? -->
- [ ] Manual Tests:
<!-- How did you test your changeset? -->
@coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] @coveo/[email protected] **/README.md **/CHANGELOG.md **/package.json README.md CHANGELOG.md package.json package-lock.json packages/ui/cra-template/template.json
<!-- For Coveo Employees only. Fill this section.
CDX-XXX
-->
## Proposed changes
<!--
Explains what are you changing in the code and provide links to relevant
issues.
This doesn't need to be over-technical, a good summary of the issues
with good explanations of the decisions should be enough.
-->
## Breaking changes
<!--
Remove this section if the PR does not include any breaking change
If your changes includes some breaking changes in the code, thoroughly
explains:
- What are the breaking changes programmatically speaking.
- What is the impact on the end-user (e.g. user cannot do X anymore).
- What motivates those changes.
-->
## Testing
- [ ] Unit Tests:
<!-- Did you write unit tests for your feature? If not, explains why?
-->
- [ ] Functionnal Tests:
<!-- Did you write functionnal tests for your feature? If not, explains
why? -->
- [ ] Manual Tests:
<!-- How did you test your changeset? -->
<!-- For Coveo Employees only. Fill this section.
CDX-XXX
-->
## Proposed changes
<!--
Explains what are you changing in the code and provide links to relevant
issues.
This doesn't need to be over-technical, a good summary of the issues
with good explanations of the decisions should be enough.
-->
## Breaking changes
<!--
Remove this section if the PR does not include any breaking change
If your changes includes some breaking changes in the code, thoroughly
explains:
- What are the breaking changes programmatically speaking.
- What is the impact on the end-user (e.g. user cannot do X anymore).
- What motivates those changes.
-->
## Testing
- [ ] Unit Tests:
<!-- Did you write unit tests for your feature? If not, explains why?
-->
- [ ] Functionnal Tests:
<!-- Did you write functionnal tests for your feature? If not, explains
why? -->
- [ ] Manual Tests:
<!-- How did you test your changeset? -->
github-actions
bot
requested review from
olamothe
and removed request for
a team
github-actions
bot
requested review from
louis-bompart and
mrrajamanickam-coveo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#1309