[ci] Implement release workflow

[Grub4K]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly
• Put an x into all the boxes [ ] relevant to your pull request (like that [x])
• Use Preview tab to see how your pull request will actually look like

---

Before submitting a pull request make sure you have:

• Searched the bugtracker for similar pull requests
• Read adding new extractor tutorial
• Read youtube-dl coding conventions and adjusted the code to meet them
• Covered the code with tests (note that PRs without tests will be REJECTED)
  • See Grub4K/youtube-dl@master for successful application of this PR, and the 2024.07.23 and 2024.07.23.1 for example releases, including changelog. Writing tests for CI results is hard
• Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

• I am the original author of this code and I am willing to release it under Unlicense

What is the purpose of your pull request?

• New feature

---

Description of your pull request and other information

Implements an automated release workflow, similar to yt-dlp's (Rewrite of the nightly workflow as an automated workflow_dispatch action). Also removes the old, obsolete build scripts in favor of using the current workflow.

It supports:

• Arbitrary version tags
• Prereleases
• Automated changelog generation
  • This is more hacked than correct since the commit format is non normative.
    make_changelog.py can be backported if the yt-dlp commit format will be adapted
• Separate build workflow
  • Each step is separated so adding more targets is trivial

After this is merged, the only barrier to publishing a new release will be running the "Release" workflow.

Closes #31585

[Grub4K]

I could not test the devscripts under 2.6, but also thats not required as far as the build process goes, so...

Additional targets can be added later to the build.yml if desired

[dirkf]

I could not test the devscripts under 2.6, but also thats not required as far as the build process goes, so...

Exactly. Anyone who wants to run the scripts with 2.6 should be able to fix any problems.

Additional targets can be added later to the build.yml if desired

Sure. But this is making the same ones as the nightly, isn't it, and that's all we need for now, except that maybe there should be two versions of the youtube-dl bundled POSIX builds, adding one with #!/usr/bin/env python3.

[Grub4K]

I think adding another target for this might not make sense. Many modern os have already switched to python pointing to python 3. Additionally, there is python-is-python3 if need be.

If you disagree ill add the target though. Just let me know what to call it

[dirkf]

I think adding another target for this might not make sense. Many modern os have already switched to python pointing to python 3. Additionally, there is python-is-python3 if need be.

If you disagree ill add the target though. Just let me know what to call it

It seems that macOS typically installs a python3 only, with no option of a python-is-python3: those users are probably less likely to understand, or be amenable to, creating a symlink. And who knows what "security" feature Apple may introduce to confound this.

If only there were some way to formulate a #! command that would find both python and python3 in some order. I haven't been able to find one that doesn't involve shipping and installing a further script, like this python_any:

#!/bin/sh
exec python3 "$@" || exec python "$@"

In all the systems where I've tried it, a sed command works (preserving the executable permission if it was set):

sed -i -e '1 s/python$/python3/' youtube-dl

As POSIX-y systems are meant to hide any platform differences between "text" and "binary" files, maybe this is good enough, once the shipped default has been decided.

Otherwise, a separate target, say youtube-dl-py3, seems to be the path of least resistance.

[Grub4K]

Done. See 2024.07.25 release for results

[Grub4K]

Side note, @dirkf, do you have access to the PyPI package?

Anyways, if needed it can easily be added based on yt-dlp workflow, or done later at any point

[Grub4K]

What is the holdup on this? Anything that can be done to get this merged?

[Grub4K]

@dirkf is this PR being considered?

[dirkf]

Definitely, but #32905 needs to be sorted before I can get back to it.