Skip to content

Conversation

@pljones
Copy link
Collaborator

@pljones pljones commented Nov 23, 2025

Short description of changes

Current builds warn:

Build for Linux .deb amd64 (artifacts+codeQL)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/

with a description on the referenced page of how to update. This change applies the description

CHANGELOG: SKIP

Context: Fixes an issue?

Deprecation notice

Does this change need documentation? What needs to be documented and how?

No.

Status of this Pull Request / What is missing until this pull request can be merged?

Let's see if the notice goes away...

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I tested my code and it does what I want
  • My code follows the style guide
  • I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
  • I've filled all the content above

AUTOBUILD: Please build all targets

@ann0see
Copy link
Member

ann0see commented Nov 28, 2025

There's a warning in the CI. Not sure if it's relevant. Probably build with all targets here gave this error. --> try without in another PR

Warning: Code scanning cannot determine the alerts introduced by this pull request, because 1 configuration present on refs/heads/main was not found:
Actions workflow (autobuild.yml)

❓  .github/workflows/autobuild.yml:release_assets/build_all_targets:false/config:

@ann0see ann0see added this to Tracking Nov 28, 2025
@github-project-automation github-project-automation bot moved this to Triage in Tracking Nov 28, 2025
@ann0see ann0see moved this from Triage to Waiting on Team in Tracking Nov 28, 2025
@pljones
Copy link
Collaborator Author

pljones commented Nov 30, 2025

There's a warning in the CI. Not sure if it's relevant. Probably build with all targets here gave this error. --> try without in another PR

I think it needs a CodeQL run against the target branch -- master -- for both configurations. So I guess we need this merged and run at least twice on master before we can check any other branches and not get warnings. (One other merge, with build_all_targets:false after this one, that is.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Waiting on Team

Development

Successfully merging this pull request may close these issues.

2 participants