-
-
Notifications
You must be signed in to change notification settings - Fork 186
fix: use version publish date instead of misleading time.modified #702
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
90309e2 to
cd500df
Compare
The npm registry's `time.modified` field can be updated by metadata changes (e.g., maintainer
additions/removals) without any versions being published. This was misleading for users trying to
assess package maintenance activity.
Changes:
- Package page now shows publish date of the displayed version
- Comparison page now shows publish date of the latest version
- Renamed "Updated" labels to "Published" throughout the app
- Added tooltip: "Date {package}@{version} was published"
cd500df to
1641d02
Compare
# Conflicts: # i18n/locales/pt-BR.json # lunaria/files/pt-BR.json
danielroe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
The npm registry's
time.modifiedfield can be updated by metadata changes (e.g., maintainer additions/removals) without any versions being published. This was misleading for users trying to assess package maintenance activity.Changes: