Per-package overrides for abandonments & community-sourced abandonments

[thomasboyt]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

42.95.2

Please tell us more about your question or problem

I was excited to adopt the new abandoned package feature when overhauling a Renovate config, but was a little disappointed to see it marked a few not-abandoned packages as abandoned and didn't provide an immediately-obvious way to override this.

We use the classnames NPM package, which is common in React applications. It hasn't been upated since December 2023, but that's because it's basically a feature-complete package - it's still maintained, as can be seen in recent GitHub activity.

I wanted to mark this as "not abandoned" in our config, but wasn't immediately clear on how. Is the only way to override the abandonmentThreshold for a specific package rule? E.g.:

{
  "packageRules": [{
    "matchPackageNames": ["classnames"],
    "abandonmentThreshold": "eternal"
  }]
}

I'll also note here that the "eternal" option isn't documented, I found it from lib/data/abandonments.json. It probably should be documented if it's the intended way to ignore abandonment for a specific package.

I have a second question which maybe could be split out to another discussion: what is the criteria for submitting a package to the shared abandonments.json? I'm a little surprised to see it hasn't been updated since being introduced last year, especially given it is linked in the docs. Could I submit a PR to add classnames, and what would be a reasonable time to set the abandonmentThreshold for it?

Logs (if relevant)

No response