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

Update release.yml #95

Merged
merged 4 commits into from
Dec 20, 2024
Merged

Update release.yml #95

merged 4 commits into from
Dec 20, 2024

Conversation

Thomas-Rowlands
Copy link
Collaborator

Fix for the publishing Github action.

Due to the nature of the action, this could need another change, but due to the error thrown this should get past the wheel building.

Fix for the publishing Github action.
Copy link
Collaborator

@AdrianDAlessandro AdrianDAlessandro left a comment

Choose a reason for hiding this comment

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

Apologies, we made a small error here. You've identified the problem correctly, but the problem is related to not using the poetry virtual environment to get the package version.

There is also an additional issue that will not be solved by this PR. The tag used in the most recent release was v1.0.1, but the version in the pyproject.toml is 1.1.0, which means this workflow will fail anyway

.github/workflows/release.yml Show resolved Hide resolved
Updated to reflect Adrian's requested changes
removed dependency installation step as per review comments.
@Thomas-Rowlands
Copy link
Collaborator Author

Edited the latest release to use the v1.1 tag to align with the pyproject.toml configuration, as I assume this was the intended release number. Combined with the changes made after review change requests, fingers crossed this sorts the problem out.

Copy link
Collaborator

@AdrianDAlessandro AdrianDAlessandro left a comment

Choose a reason for hiding this comment

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

I believe this is all good to go!

The release tag will need to be changed to v1.1.0 so it is a valid semantic version string (all three numbers are always required). Also, the associated release action will need to be re-run if changing the release tag does not trigger a re-run

@Thomas-Rowlands Thomas-Rowlands merged commit 2fefd95 into main Dec 20, 2024
9 checks passed
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