Add auto-upgrade workflow for embedded dependencies#3057
Conversation
d7f5464 to
e59afaf
Compare
e59afaf to
f371ee9
Compare
There was a problem hiding this comment.
We need to implement a slight delay window here by default to follow our delay policy: https://virtualenv.pypa.io/en/latest/explanation.html#periodic-update-mechanism
Generally we wait at least a week before we pull in a new wheel as embedded.
|
|
||
| This PR was created automatically by the [upgrade workflow](https://github.com/${{ github.repository }}/actions/workflows/upgrade.yaml). | ||
|
|
||
| > [!NOTE] |
There was a problem hiding this comment.
We could setup a PAT to allow it to run and go through 🤔
There was a problem hiding this comment.
I thought, it might be a security concern, but whose PAT we would use?
There was a problem hiding this comment.
Probably mine for now 🤔 We could make it optional, and hopefully at some point can setup a fine grained PAT https://discuss.python.org/t/fine-grained-pat-approvals-and-release-automation-in-pypa-projects/106197 so only has rights to this repo and not otherwise.
There was a problem hiding this comment.
Could be also interesting to see if we can use https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#deploy-keys here 🤔
Add a daily GitHub Actions workflow that:
Thanks for contributing, make sure you address all the checklists (for details on how see development documentation)
tox -e fix)docs/changelogfolder