WORKFLOW / Platform engineering

Turn runtime support dates into an upgrade review

Track exact Node.js and Python release cycles, preserve support-policy evidence, and attach the observations to your own service inventory.

Start with the sample ↓Actor details Read the findings →

4 saved observationsObserved October 18, 2026 UTCManual execution

REAL RECORDS / DATED EVIDENCE

Which runtime cycles need a support-policy review?

Saved at 2026-10-18T13:04:39.436Z from build 1.0.1. This preview makes no live requests.

Selected fields from the saved bounded sample
Product	Cycle	End Of Life Date	Days To End Of Life	Is Maintained
nodejs	20	2026-04-30	-171	true
nodejs	22	2027-04-30	194	true
python	3.10	2026-10-01	-17	false
python	3.11	2027-10-31	378	true

Sample CSV ↓Sample JSON ↓Exact input ↓Method & coverage

FROM DATA TO A REVIEW QUEUE

Five practical steps

Replace the four example cycles with exact versions from your own inventory. This Actor does not scan installed software.
Read endOfLifeDate and activeSupportEnds separately. A general maintained flag does not establish your entitlement to commercial or extended support.
Open vendorPolicyUrl to confirm the policy for the specific release and your support arrangement.
Join product and cycle to your inventory, then assign an owner and a proposed migration date in your review sheet.
For repeated date-change observations, enable comparePrevious with your own snapshotName and run sequentially. The supplied sample leaves history off.

Destination key: product + cycle. Keep an audit trail and preserve prior rows when a later sample is empty.

TWO WAYS TO START

Run in Apify or download the starter

Use Apify Console

Open the Actor, switch to JSON input and paste the example below.
Review current pricing, use your own account, and set a $0.05 maximum run charge.
Run manually. Review SUMMARY and results before exporting CSV into your review sheet.

Open Actor on Apify ↗

Exact sample input

{
  "watchlist": [
    {
      "product": "nodejs",
      "cycle": "20"
    },
    {
      "product": "nodejs",
      "cycle": "22"
    },
    {
      "product": "python",
      "cycle": "3.10"
    },
    {
      "product": "python",
      "cycle": "3.11"
    }
  ],
  "maxResults": 4,
  "maxRunSeconds": 120
}

Download a repeatable runner

Save these three files in one folder. The Node.js 22+ starter needs no npm packages. Add your own Apify token through your environment; the downloads contain no credentials.

Runner ↓Configuration ↓Setup guide ↓

node run-workflow.mjs --run

Execution is explicit and can incur charges. The starter saves local CSV/JSON, checks run status and coverage, and supports resuming an existing run. Connect your own spreadsheet after reviewing the output. It does not enable a schedule or send notifications.

A SMALL, EXPLAINED START

What this sample would cost at listed event rates

$0.00805

4 results × $0.002 per result, plus $0.00005 Actor Start at the FREE-tier rates observed October 18, 2026. This is a modeled event charge, not a bill or a complete account-cost estimate. Platform/API/storage usage and plan rates may differ.

The runner requests a $0.05 maximum charge. A cap can stop collection early. Check current pricing ↗.

Keep the source’s meaning

Dates come from the community-maintained endoflife.date service. The vendor policy is the follow-up authority.
Countdowns use the observation date in UTC and will change when you rerun.
A support deadline is not a vulnerability scan or proof of compliance.

Read the full Actor guide for fields and scope. See the dated report for what this specific sample supports.