Skip to content

Update yarn-upgrade.yml#20791

Merged
mergify[bot] merged 2 commits intomainfrom
epolon/ignore-types-jest
Jun 21, 2022
Merged

Update yarn-upgrade.yml#20791
mergify[bot] merged 2 commits intomainfrom
epolon/ignore-types-jest

Conversation

@iliapolo
Copy link
Copy Markdown
Contributor

In #19893, we added init-templates package.json files to our automatic upgrades mechanism. The packages jest and ts-jest were (not sure why...), added to the rejection list, i.e they specifically will not be upgraded; However, @types/jest was not added to this list, thereby creating a potential major version mismatch between them.

This is exactly what happened here: #20751

This PR rejects upgrades to @types/jest as well, to keep them in sync.


All Submissions:

Adding new Unconventional Dependencies:

  • This PR adds new unconventional dependencies following the process described here

New Features

  • Have you added the new feature to an integration test?
    • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Jun 19, 2022

@iliapolo iliapolo requested a review from a team June 19, 2022 21:43
@aws-cdk-automation aws-cdk-automation requested a review from a team June 19, 2022 21:43
@github-actions github-actions bot added the p2 label Jun 19, 2022
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jun 19, 2022
Copy link
Copy Markdown
Contributor

@corymhall corymhall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason we can't upgrade jest to 28 is because they updated the minimum supported typescript version to 4.3

https://github.com/facebook/jest/releases/tag/v28.0.0

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jun 21, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 755eed8
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit fb5ebdd into main Jun 21, 2022
@mergify mergify bot deleted the epolon/ignore-types-jest branch June 21, 2022 08:11
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jun 21, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

daschaa pushed a commit to daschaa/aws-cdk that referenced this pull request Jul 9, 2022
In aws#19893, we added init-templates `package.json` files to our automatic upgrades mechanism. The packages `jest` and `ts-jest` were (not sure why...), added to the rejection list, i.e they specifically will not be upgraded; However, `@types/jest` was not added to this list, thereby creating a potential major version mismatch between them. 

This is exactly what happened here: aws#20751

This PR rejects upgrades to `@types/jest` as well, to keep them in sync.

----

### All Submissions:

* [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)

### Adding new Unconventional Dependencies:

* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies)

### New Features

* [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
	* [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)?

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contribution/core This is a PR that came from AWS. p2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants