You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some recent issues have emerged with the EOL certifier introduced in #2215, specifically its failure to produce EOL-related HasMetadata nodes and some CLI issues. Currently, the EOL-on-ingest functionality isn’t validated in our end-to-end tests, making it difficult to prevent regressions or confirm fixes.
Describe the solution you’d like
Following the pattern from #2142, we can enhance the e2e test suite by adding the --add-eol-on-ingest flag. We’d then target a package known to have passed its EOL according to endoflife.date data, ensuring the certifier works as intended in a full integration scenario.
Describe alternatives you’ve considered
N/A
Additional context
Before implementing this, let’s allow recent corrective PRs (#2394 and #2391) to be merged. Once these changes are in, I’ll open a PR to add the e2e coverage and address any lingering issues.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some recent issues have emerged with the EOL certifier introduced in #2215, specifically its failure to produce EOL-related
HasMetadata
nodes and some CLI issues. Currently, the EOL-on-ingest functionality isn’t validated in our end-to-end tests, making it difficult to prevent regressions or confirm fixes.Describe the solution you’d like
Following the pattern from #2142, we can enhance the e2e test suite by adding the
--add-eol-on-ingest
flag. We’d then target a package known to have passed its EOL according to endoflife.date data, ensuring the certifier works as intended in a full integration scenario.Describe alternatives you’ve considered
N/A
Additional context
Before implementing this, let’s allow recent corrective PRs (#2394 and #2391) to be merged. Once these changes are in, I’ll open a PR to add the e2e coverage and address any lingering issues.
The text was updated successfully, but these errors were encountered: