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
I'm going through dependency upgrades and this package is getting updates in npm, but I don't see them here in the referenced repository.
CHANGELOG.md and the published tags are really out of date, eroding trust that the code I can see in GitHub is the code I'm getting from NPM (although, I realize that what is in GitHub is not a guarantee of what is in npm)
from npm's new code tab, I can see the correct current package version of 6.2.8 in package.json, which indicates that this is still the current repository, but the code in this repository is out of date. Is this maintained by someone else now?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The repo is currently maintained by users and myself. We can improve the changelogs. To move forward for the next major version we need to fix some core issues first
I'm going through dependency upgrades and this package is getting updates in npm, but I don't see them here in the referenced repository.
CHANGELOG.md and the published tags are really out of date, eroding trust that the code I can see in GitHub is the code I'm getting from NPM (although, I realize that what is in GitHub is not a guarantee of what is in npm)
from npm's new code tab, I can see the correct current package version of 6.2.8 in package.json, which indicates that this is still the current repository, but the code in this repository is out of date. Is this maintained by someone else now?
The text was updated successfully, but these errors were encountered: