Upgrade external GitHub Actions actions (Node 20)

[jonathanlinat]

This PR aims to eliminate these warning messages in GitHub Actions as the entire infrastructure is migrating to Node 20:

The external actions must be upgraded to their newest available version.

Reference: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

[jonathanlinat]

It is important to note that this specific action must be upgraded to Node 20.

---

@kduske I have created a PR to address this specific case: TrenchBroom/clean-commit-action#1

Once the PR is merged, I must update the current TrenchBroom GitHub Actions workflow(s) to upgrade the corresponding action to version v0.8.0.

[jonathanlinat]

Regarding this issue, we might need to rename the linux artifact based on the version of Ubuntu.

[kduske]

Regarding this issue, we might need to rename the linux artifact based on the version of Ubuntu.

Can you explain? This has worked until now.

[jonathanlinat]

Regarding this issue, we might need to rename the linux artifact based on the version of Ubuntu.

Can you explain? This has worked until now.

Sure!

I had to update the tool this project uses to send files to GitHub, and I think the way it names files changed too.

You can see that the file made for Ubuntu 22.04 was sent before the one for Ubuntu 20.04. But no matter which version of Ubuntu it used, both files ended up with the name linux.

This is causing a problem because there's already an uploaded file named linux, and it won't let it upload another one with the same name.

To fix this, the names of the files need to be changed to include the Ubuntu version they're for, like linux-20.04 and linux-22.04. We might also only need to tweak the settings of the action. I have to investigate that.

Do you want me to address this issue in this current PR or do you prefer I address it in another one?

[jonathanlinat]

It is important to note that this specific action must be upgraded to Node 20.

@kduske I have created a PR to address this specific case: TrenchBroom/clean-commit-action#1

Once the PR is merged, I must update the current TrenchBroom GitHub Actions workflow(s) to upgrade the corresponding action to version 0.8.0.

Another important thing is I need you to manually create a tag to use the latest version of clean-commit-action. The tag must be named v0.8.0. I don't have the permission to proceed in this repository.

[kduske]

I see. It would be better to address this in this PR before the action gets updated. These files must already be renamed when we publish a release, because they have much more prescriptive names then. Maybe we could just move that existing renaming step to before the file gets uploaded?

[kduske]

I have created the v0.8.0 tag in https://github.com/TrenchBroom/clean-commit-action/tags

[jonathanlinat]

Something's not working properly with the new version of clean-commit-action. I'll take a look.

[jonathanlinat]

Something's not working properly with the new version of clean-commit-action. I'll take a look.

@kduske This PR is designed to address the malfunction in the clean-commit-action: https://github.com/TrenchBroom/clean-commit-action/pull/2/files

I cannot guarantee that it will work before merging the PR. We will figure it out after merging it.

Important: Please note that once it's merged, a new tag, v0.8.1, needs to be created.

---

To resolve the problem with a Linux artifact that was previously uploaded, the artifacts have been renamed according to the following convention:

The workflow does not fail anymore, and the artifacts are correctly uploaded.

[jonathanlinat]

Just an additional thought.

Personally, I feel it would be wise to discontinue support for Windows (x32). It seems to me that not many mappers are using such an outdated architecture these days.

[kduske]

Thanks, I have created the tag!

[jonathanlinat]

@kduske My apologies. I completely overlooked running the ./build.sh command in my Terminal, and as a result, the same problem occurred in the pipeline because of an unupdated dist file.

Here's the PR that should definitely fix this issue: TrenchBroom/clean-commit-action#3

Important: As noted in that PR, once it's merged, we'll need to create a new tag: v0.8.2

[kduske]

Ok, I have created the release and deleted the other ones.

[jonathanlinat]

@kduske We're good now! 😃

[jonathanlinat]

For those two issues, there is a pending PR ready to be merged in the corresponding repository.

However, to not block the merge of this current PR, I can create another one in the future once this action is updated: jurplel/install-qt-action#222