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

Move the check_release.yml to its own workflow #2191

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

jtpio
Copy link
Member

@jtpio jtpio commented Nov 14, 2024

  • Move the check_release step to a separate workflow, so it's easier to see if it passes
  • And add an extra step to upload the artifacts built by the releaser, so it's easier to test PRs locally by installing the built wheel from a branch.

@jtpio jtpio changed the title Create check-release.yml Move the check_release.yml to its own workflow Nov 14, 2024
@jtpio jtpio closed this Nov 14, 2024
@jtpio jtpio reopened this Nov 14, 2024
@jtpio jtpio marked this pull request as ready for review November 14, 2024 10:21
@jtpio
Copy link
Member Author

jtpio commented Dec 6, 2024

@martinRenou I was wondering if this was maybe ready to be merged?

Having the built artifacts could help test changes from other PRs more easily, for example #2178.

Copy link
Member

@martinRenou martinRenou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@martinRenou martinRenou enabled auto-merge (squash) December 6, 2024 11:19
@krassowski
Copy link
Member

test_check does not pass because it is waiting for check_release:

tests_check: # This job does nothing and is only used for the branch protection
if: always()
needs:
- coverage
- test_lint
- test_minimum_versions
- test_prereleases
- check_links
- check_release
- test_sdist

It would need to be removed from it and added as a separate protection rule

auto-merge was automatically disabled January 2, 2025 17:41

Head branch was pushed to by a user without write access

@jtpio
Copy link
Member Author

jtpio commented Jan 2, 2025

It would need to be removed from it and added as a separate protection rule

Done in 5541bdb.

However I don't have access to the repo settings to enable the protection rule in case we want to add one (not sure if this may have an impact on the releaser though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants