You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently a new version of this library was pushed to PyPI (https://pypi.org/project/envs/1.4/) however there's no description, changelog, or history in PyPI. Similarly, there's no documentation of this version in the repo itself, in either the README or HISTORY files. There's also only one tag in the repository, for a release from 5 years ago. According to PyPI, 14 versions have been released since that point, but its impossible to tell which changes in the repo belong to which version of the package, or to perform any typical kind of diff between them at all.
Going forward, do you have any plans to implement any practices around the release notes, changelog, and tags at release points in history? While all of these would be preferred, realistically any one of them could get the job done if kept up with consistently.
The text was updated successfully, but these errors were encountered:
The closest thing we can do about this will be in the HISTORY.md, as for the description, it should use the README.md but it seems that we weren't able to configure setuptools to use our README.md. We'll release a fix for this and for the changelogs, we'll constantly update our HISTORY.md instead, and of course, the README as well.
Recently a new version of this library was pushed to PyPI (https://pypi.org/project/envs/1.4/) however there's no description, changelog, or history in PyPI. Similarly, there's no documentation of this version in the repo itself, in either the README or HISTORY files. There's also only one tag in the repository, for a release from 5 years ago. According to PyPI, 14 versions have been released since that point, but its impossible to tell which changes in the repo belong to which version of the package, or to perform any typical kind of diff between them at all.
Going forward, do you have any plans to implement any practices around the release notes, changelog, and tags at release points in history? While all of these would be preferred, realistically any one of them could get the job done if kept up with consistently.
The text was updated successfully, but these errors were encountered: