Skip to content

chore: use a different yarn-upgrade branch for v1#21211

Merged
mergify[bot] merged 2 commits intoaws:mainfrom
corymhall:corymhall/fix-yarn-upgrade-v1
Jul 18, 2022
Merged

chore: use a different yarn-upgrade branch for v1#21211
mergify[bot] merged 2 commits intoaws:mainfrom
corymhall:corymhall/fix-yarn-upgrade-v1

Conversation

@corymhall
Copy link
Copy Markdown
Contributor

Both the v1 and v2 yarn-upgrade workflow use the same
automation/yarn-upgrade branch. This causes issues if they are both
active at the same time.

Use a different branch for v1.


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

Both the v1 and v2 yarn-upgrade workflow use the same
`automation/yarn-upgrade` branch. This causes issues if they are both
active at the same time.

Use a different branch for v1.
@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Jul 18, 2022

@github-actions github-actions bot added the p2 label Jul 18, 2022
@aws-cdk-automation aws-cdk-automation requested a review from a team July 18, 2022 18:08
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jul 18, 2022
@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

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

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

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 18, 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).

@mergify mergify bot merged commit e36cc7b into aws:main Jul 18, 2022
@corymhall corymhall deleted the corymhall/fix-yarn-upgrade-v1 branch July 18, 2022 19:11
comcalvi pushed a commit to comcalvi/aws-cdk that referenced this pull request Jul 25, 2022
Both the v1 and v2 yarn-upgrade workflow use the same
`automation/yarn-upgrade` branch. This causes issues if they are both
active at the same time.

Use a different branch for v1.


----

### All Submissions:

* [ ] 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