Bump github/codeql-action from 4.31.10 to 4.31.11

[ikostan]

Bumps github/codeql-action from 4.31.10 to 4.31.11.

• Release notes
• Commits

---

updated-dependencies:

• dependency-name: github/codeql-action dependency-version: 4.31.11 dependency-type: direct:production update-type: version-update:semver-patch ...

---

name: Default Pull Request Template
about: Suggesting changes to SkyLockAssault
title: ''
labels: ''
assignees: ''

Description

What does this PR do? (e.g., "Fixes player jump physics in level 2" or "Adds
new enemy AI script")

Related Issue

Closes #ISSUE_NUMBER (if applicable)

Changes

• List key changes here (e.g., "Updated Jump.gd to use Godot 4.4's new Tween
  system")
• Any breaking changes? (e.g., "Deprecated old signal; migrate to new one")

Testing

• Ran the game in Godot v4.5 editor—describe what you tested (e.g., "Jump
  works on Win10 with 60 FPS")
• Any new unit tests added? (Link to test scene if yes)
• Screenshots/GIFs if UI-related: (Attach below)

Checklist

• Code follows Godot style guide (e.g., snake_case for variables)
• No console errors in editor/output
• Ready for review!

Additional Notes

Anything else? (e.g., "Tested on Win10 64-bit; needs Linux validation")

Summary by Sourcery

Update GitHub CodeQL-related workflow actions to the latest patch versions.

Build:

• Bump github/codeql-action init, autobuild, analyze, and upload-sarif steps from v4.31.10 to v4.31.11 across security workflows.
• Update the pinned SHA for github/codeql-action/upload-sarif used in the Trivy workflow to the corresponding latest stable commit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates all usages of github/codeql-action in CI workflows from version 4.31.10 to 4.31.11, including both tag-based and pinned-SHA references used for CodeQL initialization, analysis, and SARIF uploads.

File-Level Changes

Change	Details	Files
Bump CodeQL init/autobuild/analyze steps to v4.31.11 in the main CodeQL workflow.	Update the CodeQL initialization step to use github/codeql-action/init@v4.31.11 instead of v4.31.10. Update the autobuild step to use github/codeql-action/autobuild@v4.31.11 instead of v4.31.10. Update the analysis step to use github/codeql-action/analyze@v4.31.11 instead of v4.31.10.	.github/workflows/codeql.yml
Bump CodeQL SARIF upload action references to v4.31.11 in Snyk workflows.	Update the Snyk Code SARIF upload step to use github/codeql-action/upload-sarif@v4.31.11 instead of v4.31.10. Update the Snyk Open Source SARIF upload step to use github/codeql-action/upload-sarif@v4.31.11 instead of v4.31.10.	.github/workflows/snyk.yml
Update the pinned SHA for the CodeQL SARIF upload action in the Trivy workflow to the commit corresponding to v3.31.0.	Replace the previous github/codeql-action/upload-sarif pinned SHA with a new SHA while keeping the version comment at v3.31.0. Ensure the Trivy SARIF upload step continues to upload scan results to GitHub Security using the updated commit reference.	.github/workflows/trivy.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The Trivy workflow still comments that the pinned SHA corresponds to v3.31.0 and an old date, but the SHA was updated—please confirm the actual version for this commit and update the inline comment to match so future maintainers aren’t misled.
• In .github/workflows, you’re mixing versioned tags (e.g., @v4.31.11) with a pinned SHA for the same action; consider standardizing on either pinned SHAs or version tags for github/codeql-action to keep the update strategy consistent across workflows.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The Trivy workflow still comments that the pinned SHA corresponds to `v3.31.0` and an old date, but the SHA was updated—please confirm the actual version for this commit and update the inline comment to match so future maintainers aren’t misled.
- In `.github/workflows`, you’re mixing versioned tags (e.g., `@v4.31.11`) with a pinned SHA for the same action; consider standardizing on either pinned SHAs or version tags for `github/codeql-action` to keep the update strategy consistent across workflows.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}