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

version bump v2.6.0 #164

Merged
merged 1 commit into from
Feb 13, 2024
Merged

version bump v2.6.0 #164

merged 1 commit into from
Feb 13, 2024

Conversation

ERosendo
Copy link
Contributor

No description provided.

@ERosendo ERosendo force-pushed the new-release-2.6.0 branch 2 times, most recently from b396ca9 to c227f72 Compare February 13, 2024 01:26
Copy link
Contributor

The Eyecite Report 👁️

Gains and Losses

There were 0 gains and 0 losses.

Click here to see details.
id Gain Loss

Time Chart

image

Generated Files

Branch 1 Output
Branch 2 Output
Full Output CSV

@ERosendo
Copy link
Contributor Author

ERosendo commented Feb 13, 2024

@mlissner While the Pdoc action is now working correctly, the PyPI action is unfortunately failing. It appears that one of the updates within this PR may have triggered a release. The new version can be found here: https://pypi.org/project/eyecite/

I've verified that the published .tar file includes the changes listed in the CHANGES.md file, and the pyproject.toml file also reflects the correct version. Based on this, I believe it's safe to merge this PR, I'll will be more cautious in the future.

@mlissner mlissner merged commit 50f372a into main Feb 13, 2024
14 of 15 checks passed
@mlissner mlissner deleted the new-release-2.6.0 branch February 13, 2024 03:50
@mlissner
Copy link
Member

Great, thanks.

@mattdahl
Copy link
Contributor

Just circling back to this, I see on pypi that 2.6.0 has been released, but 2.5.3, 2.5.4, and 2.5.5 have not been yanked yet.

@mlissner
Copy link
Member

Oops, sorry, thanks for the reminder. Those versions are now yanked, so I think now we get to see what kind of fallout we incur (hopefully none?).

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