Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: configure dependabot to ignore jest upgrade #7662

Closed
wants to merge 1 commit into from

Conversation

NetaNir
Copy link
Contributor

@NetaNir NetaNir commented Apr 29, 2020

Commit Message

chore: dependabot ignore jest
Jest v25.5.0 breaks CDK tests, temporarily configuring dependabot to ignore jest upgrade.
Tracking p0: #7657

End Commit Message


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

@NetaNir NetaNir requested a review from a team April 29, 2020 02:19
@NetaNir NetaNir changed the title chore: dependabot ignore jest chore: configure dependabot to ignore jest upgrade Apr 29, 2020
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Apr 29, 2020
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: d831684
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

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

@iliapolo
Copy link
Contributor

Closing this for now as we plan on creating a fix that will handle this version of jest properly.

@iliapolo iliapolo closed this Apr 29, 2020
@NetaNir NetaNir deleted the neta/temp-fix-no-jest-upgrade branch May 8, 2020 05:42
@NetaNir NetaNir restored the neta/temp-fix-no-jest-upgrade branch May 8, 2020 05:42
@NetaNir NetaNir deleted the neta/temp-fix-no-jest-upgrade branch June 12, 2020 02:14
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants