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

[BUG] github/pypi release possible wrong date? #3456

Closed
2 tasks done
Elypha opened this issue Aug 18, 2024 · 4 comments
Closed
2 tasks done

[BUG] github/pypi release possible wrong date? #3456

Elypha opened this issue Aug 18, 2024 · 4 comments

Comments

@Elypha
Copy link

Elypha commented Aug 18, 2024

Describe the bug

Hello,

This is not essentially a bug but just found that a merged commit 2a33a77 from more than a year ago was actually not included in the latest release in Feb 2024.
And, for the date - since the release comment says 2023-02-28, may I know if that was just an old release drafted at 2023-02-28 and published a year later due to some reason, or it's simply a typo.
If it's the former case then that commit shouldn't be included indeed which is okay, but as it seems to me more like a typo I'm submitting this issue to ask about it.

Platform

Click to expand

What platform (Win/Linux/Mac) are you running on? What terminal software are you using?

I may ask you to copy and paste the output of the following commands. It may save some time if you do it now.

If you're using Rich in a terminal:

python -m rich.diagnose
pip freeze | grep rich

If you're using Rich in a Jupyter Notebook, run the following snippet in a cell
and paste the output in your bug report.

from rich.diagnose import report
report()
Copy link

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

This is an automated reply, generated by FAQtory

@TomJGooding
Copy link
Contributor

The commit was merged in July 2024 and the Changelog shows this change is unreleased?

@willmcgugan
Copy link
Collaborator

There was a large backlog, we're just getting caught up. Might have taken a while to be merged.

Copy link

I hope we solved your problem.

If you like using Rich, you might also enjoy Textual

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

No branches or pull requests

3 participants