Automate pulling new components version

[koplo199]

See the entire discussion in bottlesdevs/Bottles#2223

TODO before merging:

• Fork koplo199/actions-download-asset in the bottlesdevs organization. It is the action used to find and pull new stable versions. Forking is mandatory as upstream is not vastly used, contains multiple bugs, outdated dependencies, and is lacking required features. Replaced by GitHub CLI

• Fork koplo199/action-gh-release in the bottlesdevs organization. It is the action used to upload archives when required. Forking is strongly advised as upstream has outdated dependencies and its maintainer hasn't been active since april. However in its current state it is functional and is vastly used, so forking is not mandatory. In fact, if action-gh-release/pull/275 was merged, there would be no reason to fork it anymore. Merged upstream!

• Add PAT as actions secret (see [Poll]: Experimental versions of dxvk, vkd3d Bottles#2223 (comment))

Please do not accept new PR in the meantime (like #180), as it initially requires a lot of manual processing to create the adequate new files, and it would probably drive me insane having to do it again

[koplo199]

It is possible to monitor what the first pull request of the CI would look like here

[mirkobrombin]

(still reviewing, I'm busy with other projects), about the 2 forks, are you going to maintain them? :D

[koplo199]

(still reviewing, I'm busy with other projects), about the 2 forks, are you going to maintain them? :D

😅

Honestly: in the very long term, probably not.
And this is precisely why I will replace them by GitHub CLI commands in a future PR, from what I read it could be used to achieve the same result, while being officially endorsed by GitHub.

But I would like this PR to get merged first, as it will add some substantial complexity to the code I prefer to implement it in a distinct PR. Also, and I guess it's human, it will motivate me to work on it a lot more (and will spare me the obnoxious task of manually creating files/entries for every PR that get merged in the meantime) 👼

[orowith2os]

One more thing, possibly wait for my other cleanup PRs before merging this, if it ever does get accepted.

[koplo199]

One more thing, possibly wait for my other cleanup PRs before merging this, if it ever does get accepted.

I would prefer the other way around, thank you.

[orowith2os]

One more thing, possibly wait for my other cleanup PRs before merging this, if it ever does get accepted.

I would prefer the other way around, thank you.

Merging this before my PR would make it harder to clean up, since I'd then have to update your checker to use those new, updated paths for components.

Better to have the clean PR merged first, then this, so that it Just Works more or less immediately after being merged.

[koplo199]

Merging this before my PR would make it harder to clean up, since I'd then have to update your checker to use those new, updated paths for components.

Merging the clean up before this PR would make it harder to update my checker, since I'd then have to use your new, updated paths for components.

Better to have the clean PR merged first, then this, so that it Just Works more or less immediately after being merged.

Better to have this PR merged first, then the cleanup, so that it Just Breaks more or less immediately after being merged and you'll have to fix it yourself instead of me.

[mirkobrombin]

Everything looks fine and ready for merge. Just to be sure, this doesn't require Bottles side changes right?

[koplo199]

Everything looks fine and ready for merge. Just to be sure, this doesn't require Bottles side changes right?

Correct!

[koplo199]

Yay merged 🎉

Is the PAT already set? If it is not configured pull requests won't be created, to configure it:

From any account (could very well be a newly created burner account like @bottlesdevs-components[BOT] or something) do
(Account) Settings -> Developer settings -> Personal access tokens -> Tokens (classic) -> Generate new token (classic) -> public_repo (No expiration)

Then copy paste it into
(Repository) Settings -> Secrets -> Actions -> New repository secret -> Name = PAT