Skip to content

Conversation

@ramosv
Copy link
Member

@ramosv ramosv commented Jul 13, 2025

Fix bug related to publish.yml attempt 2

@ramosv ramosv requested a review from Copilot July 13, 2025 21:39
@ramosv ramosv self-assigned this Jul 13, 2025
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the Twine upload step in the GitHub Actions publish.yml to install Twine at runtime and point to a new package registry endpoint.

  • Install or upgrade pip and twine before uploading
  • Change the --repository-url to the GitHub Packages API for Python
  • Keep the existing dist/* artifact path unchanged
Comments suppressed due to low confidence (1)

.github/workflows/publish.yml:34

  • The repository URL is now pointing to the GitHub Packages API rather than the public PyPI legacy endpoint. If the intention is to publish to PyPI.org, change this to https://upload.pypi.org/legacy/. If you mean to target GitHub Packages, consider renaming the job or step to reflect that.
            --repository-url https://api.github.com/orgs/${{ github.repository_owner }}/packages/pypi/upload \

run: |
twine upload \
--repository-url https://upload.pypi.github.io/UCD-BDLab/BioNeuralNet \
python -m pip install --upgrade pip twine
Copy link

Copilot AI Jul 13, 2025

Choose a reason for hiding this comment

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

[nitpick] Installing pip and twine on every workflow run can slow down CI. Consider using actions/setup-python with a pre-cached environment or leveraging actions/cache to speed up dependency installation.

Copilot uses AI. Check for mistakes.
Copy link
Member Author

Choose a reason for hiding this comment

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

that's actually not a bad suggestion for once.

@ramosv ramosv merged commit e1cd5d4 into main Jul 13, 2025
11 checks passed
@ramosv
Copy link
Member Author

ramosv commented Jul 13, 2025

All test checks have passed.
Since no code change I will merge to main bypassing rule.

@ramosv ramosv deleted the update-publish-yml-release-on-tag-two branch October 9, 2025 17:24
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.

2 participants