-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
CI: Update build and release dependencies to be referenced by SHA #9177
CI: Update build and release dependencies to be referenced by SHA #9177
Conversation
…ed using StepSecurity Signed-off-by: StepSecurity Bot <[email protected]>
…sses Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
…ashes Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
The flag is needed to create hash-pinned requirements for pip and setup-tools. Find more information about this at these issues from [pip-tools](jazzband/pip-tools#806) and from [pip](pypa/pip#6459). Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
CI seems unhappy. Once it's green I'll review. Thanks for working on this! |
…teps Using the actions/checkout to download the requirements.txt was erasing some necessary files that came from previous steps. Thus, this commit changes moves the checkout action to the beginnig of the jobs. Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
CI passing now! It was a problem with a misplaced actions/checkout call that was erasing files created by previous steps. That said, I choose to use this actions/checkout to get the requirements.txt from the repository, taking into account the exact same commit/version that is being run at the CI. If you have any better ideas on how to do it, let me know and I'd be happy to review and refactor my changes. |
I've got this on my TODO to review this evening. Thanks
…On Wed, Jul 5, 2023 at 2:18 PM diogoteles08 ***@***.***> wrote:
CI passing now! It was a problem with a misplaced actions/checkout call that was erasing files created by previous steps.
That said, I choose to use this actions/checkout to get the requirements.txt from the repository, taking into account the exact same commit/version that is being run at the CI. If you have any better ideas on how to do it, let me know and I'd be happy to review and refactor my changes.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please move the requirements files from github/workflows/requirements/
to .github/requirements/
Very close on this. Thanks for your work!
…m code Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
…uild requirements file Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
beaba75
to
916a9bc
Compare
Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
Moved from .github/workflows/requirements/ to .github/requirements/ Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
…relation Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
… pyproject.toml Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
When calling actions/checkout , we were passing the `ref` parameter as `github.ref`, but it will likely be always main, or the vary same value as the default for this parameter.
Thanks for working on this @diogoteles08 |
Implementation of second part of the issue #9073