Update summarize workflow to adjust download counts for pre-releases

[gsheni]

Context

When summarizing the download counts for different ecosystems, we include downloads for pre-releases. However, we may want to adjust download counts for libraries (with regard to pre-releases) to provide a more precise assessment of usage.

Description

A pre-release is defined as a release to support testing by users prior to a final release, identified by version segments such as:

• 1.2.3dev0 (development release)
• 1.2rc3 (release candidate)
• 1.2.0a1 (alpha release)
• 1.2.0b1 (beta release)

When summarizing the ecosystem download counts, we have the following options to handle pre-release downloads:

1. Count all pre-release downloads for all ecosystems (current behavior)
2. Do not count pre-release downloads for any ecosystem. This would the lower download counts for all ecosystems.
3. Do not count pre-release downloads for libraries in SDV ecosystem. However, count pre-release downloads for external libraries. This would only lower SDV ecosystem download counts.

A informed decision should be made on how to handle pre-release downloads and the summarize workflow should be updated.

Deliverables

• Update Daily Summarize Workflow with the decided option (if different than current behavior)