Releases: ChangesWatch/deprecation-scan
Release list
v1.1.0 — grouped deprecation intelligence
Adds grouped deprecation readiness results in the GitHub Job Summary, urgent/high/attention prioritization, direct/transitive context, dependency paths, migration recipe fields, evidence links, package status links, sanitized registry annotations, and a separate coverage section. Warn-only behavior remains unchanged.
v1.0.5
Registry deprecation findings now link to an explicitly labelled, version-specific Changes.Watch npm package-status page. Verified catalog findings keep their separate editorial card links.
v1.0.4
Verified deprecation findings in the GitHub Job Summary now link directly to their Changes.Watch update card and official source. Registry-only findings remain linked only to registry evidence until a verified Changes.Watch card exists.
v1.0.3
Raised the opt-in registry coverage cap to 2,000 unique exact package versions. The safe default remains 500; large repositories can now request complete coverage within the bounded concurrent scan.
v1.0.2
Expanded bounded npm registry coverage: the Action now checks up to 500 unique exact package versions by default (configurable up to 1,000), deduplicates repeated versions, uses bounded concurrency, and reports checked/candidate coverage.