Create dependabot rule to upgrade TorchFix version #3208
Conversation
The parameters are from From https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file ### Testing On my own fork https://github.com/huydhn/executorch/blob/main/.github/dependabot.yml, and the PR to upgrade TorchFix is created successfully huydhn#2
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/3208
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 27dc07c with merge base 8dc54d5 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
facebook-github-bot
added
the
CLA Signed
|
@huydhn has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
Why not just unpin? |
Like PT, ET is currently pinned all their dependencies as part of Docker image build, so I think having a PR like huydhn#2 would allow ET owners to control the upgrade process and land the PR only when it looks good. Also, creating a dependabot.yml might be useful for other packages in the future. |
|
@huydhn has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
I switch the reviewer to |
|
There is a chance that new TorchFix release will introduce CI failures after new rules added to TorchFix. |
|
@pytorchbot drci |
The parameters are from From https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
Testing
On my own fork https://github.com/huydhn/executorch/blob/main/.github/dependabot.yml, and the PR to upgrade TorchFix is created successfully huydhn#2