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

Flag packages as abandoned in lookup results #34128

Open
rarkins opened this issue Feb 10, 2025 · 0 comments
Open

Flag packages as abandoned in lookup results #34128

rarkins opened this issue Feb 10, 2025 · 0 comments
Assignees
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Feb 10, 2025

Describe the proposed change(s).

For each package we look up, we should calculate the most recent release date of all releases in the result (where releaseTimestamp is present). This should not be "the release date of the release flagged as latest" - instead it should be the latest/most recent release timestamp of all releases in the package, including beta/non-latest releases. This field could be stored as lastReleaseTimestamp at the package level. It should be calculated and stored before filtering such as allowedVersions is applied. i.e. in the datasource/index processing before passing back to the worker lookup process.

In addition, a new configuration option should be added: abandonmentThreshold, which supports the same date range syntax as minimumReleaseAge. It should default to null (no threshold) but if it is defined then it should be used to calculate a new isAbandoned boolean field to be added to packages, based on the lastReleaseTimestamp value calculated earlier. The field isAbandoned should be present (true or false) only if both lastReleaseTimestamp and abandonmentThreshold are defined for a package - otherwise undefined. Such logic could be done in the worker and is not essential in the datasource itself.

@rarkins rarkins added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality) labels Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

2 participants