(python) Outdated, build failing with null

[JPRuskin]

Checklist

• I have checked the moderation queue that no new version has been submitted (only visible when logged in), or the submitted package version has failed the automated checks.

Please navigate to the following link to view the moderation queue.

• I have verified that the new version is a stable release.
• I have looked to see if there are any Bug reports that prevents a new version being submitted and that no existing Outdated Reports have been created.
• I have verified the new version has a Windows binary (EXE or MSI installer, Zip or other archive, etc).
• I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.

New Software Version

3.12.7, 3.11.10

Download location

No response

Package Page

No response

[karig]

There will be no Windows builds for version 3.11.10 (and later), but there is in addition to 3.12.7 now the new official release 3.13.0 (but also not via chocolateys python313 package).

[Dutcho]

additional to what @karig mentioned, also Python 3.14.0a1 - Oct. 15, 2024 as (very early) pre-release

My understanding is this should upgrade auto-magically. If not, I'd be happy to draft a PR with s/3.12.6/3.12.7/, s/3.13.0rc2/3.13.0/, and insertion of 3.14.0a1.

[chadlwilson]

it looks like the autoupdate bot is broken, as nothing seems to have updated since 13 Oct: https://gist.github.com/choco-bot/a14b1e5bfaf70839b338eb1ab7f8226f

[JPRuskin]

it looks like the autoupdate bot is broken, as nothing seems to have updated since 13 Oct: https://gist.github.com/choco-bot/a14b1e5bfaf70839b338eb1ab7f8226f

Hm. The gist hasn't been updated, but I can see update activity in the commits. I'll have a look into that separately.

Edit: I'm enjoying that clicking on the 10k revisions failed to load on my first attempt. 😅

I guess it's possible we've gone over some fun limit!

[chadlwilson]

Ahh, OK. Updates aren't coming in for NodeJS either, which is why I was poking around here to see what might be wrong. I guess first step is to get the update logs/summary working again so we can see if there are errors needing resolving.

[JPRuskin]

As there's no template for this kind of issue in this repository (fun, making a note), I'll say here that there appears to be an issue with the json we're passing to GitHub, and I'm going to go discuss it / continue investigating it in Discord and/or the community mail group for now.

Running Gist
  ERROR:  
    {"message":"Problems parsing JSON","documentation_url":"https://docs.github.com/rest/gists/gists#update-a-gist","status":"400"}

WRT Node (again, completely the wrong place, but just to get you unblocked if you were looking for this, and I'll edit it out if I get the reports fixed):

   [125/243] nodejs ERROR: 
     Can't validate URL 
     Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found.":https://nodejs.org/dist/v23.0.0/node-v23.0.0-x86.msi (19.01s)

[chadlwilson]

Thanks @JPRuskin thats helpful. Created #2557 which will hopefully unblock nodejs updates. Sorry for the distraction here. Back to Python!