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

ci: Include distribution assets in each GitHub release #32

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

garrison
Copy link
Member

@coveralls
Copy link

Pull Request Test Coverage Report for Build 10841469671

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 10832955808: 0.0%
Covered Lines: 297
Relevant Lines: 297

💛 - Coveralls

@@ -40,6 +40,5 @@ jobs:
if: always()
uses: coverallsapp/github-action@v2
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
Copy link
Member Author

Choose a reason for hiding this comment

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

This seems to be the default, as it seems to be safe to drop this line.

with:
ref: ${{ github.ref_name }}
Copy link
Member Author

Choose a reason for hiding this comment

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

Likewise, not necessary to specify.

runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up Python
Copy link
Member Author

Choose a reason for hiding this comment

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

Should specify Python 3.12 here explicitly. When Python 3.13 is released, there may be a short time before symengine wheels are available, and we don't want releases to fail in the meantime.

For this reason we really ought also to run this "build" step upon every push to main, as suggested in the pypa docs.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, those seem like reasonable ideas. Having this run on main should work if we loosen the run conditions at the top of this file but restrict the conditions for the second and third job in here.

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

Successfully merging this pull request may close these issues.

3 participants