Bump github/codeql-action from 2.22.11 to 3.27.9

[dependabot]

Bumps github/codeql-action from 2.22.11 to 3.27.9.

Release notes

Sourced from github/codeql-action's releases.

v3.27.9

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.9 - 12 Dec 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.7

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.7 - 10 Dec 2024

• We are rolling out a change in December 2024 that will extract the CodeQL bundle directly to the toolcache to improve performance. #2631
• Update default CodeQL bundle version to 2.20.0. #2636

See the full CHANGELOG.md for more information.

v3.27.6

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.6 - 03 Dec 2024

• Update default CodeQL bundle version to 2.19.4. #2626

See the full CHANGELOG.md for more information.

v3.27.5

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.5 - 19 Nov 2024

No user facing changes.

... (truncated)

Commits

• df409f7 Merge pull request #2649 from github/update-v3.27.9-7972a42f3
• feca44d Update changelog for v3.27.9
• 7972a42 Merge pull request #2648 from github/aeisenberg/add-environment
• 44bf16d Merge pull request #2646 from github/mergeback/v3.27.8-to-main-8a93837a
• f124ad0 Adds an environment for creating releases
• 9275370 Update checked-in dependencies
• a059a7a Update changelog and version after v3.27.8
• 8a93837 Merge pull request #2645 from github/update-v3.27.8-9cfbef4bd
• 90a2700 Update changelog for v3.27.8
• 9cfbef4 Merge pull request #2644 from github/aeisenberg/use-app-token-for-release
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

CI:

• Update CodeQL Action to version 3.27.9 in GitHub workflows for improved performance and compatibility with Node 20.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the GitHub CodeQL Action from version 2.22.11 to 3.27.9. The main change is the upgrade to Node 20 support in v3, while maintaining the same functionality as v2. The update includes several minor version improvements, including performance enhancements for CodeQL bundle extraction and updates to the default CodeQL bundle versions.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update CodeQL Action version references in GitHub workflows	Update CodeQL initialization action to v3.27.9 Update CodeQL analysis action to v3.27.9 Update SARIF upload action commit reference	.github/workflows/codeql-analysis.yml .github/workflows/scorecard.yml
Upgrade to Node 20 compatible version	Switch from Node 16 (v2) to Node 20 (v3) runtime environment Maintain functional parity between v2 and v3 versions	.github/workflows/codeql-analysis.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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[gitworkflows]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[deepsource-io]

Here's the code health analysis summary for commits 983802d..f754daf. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

Action: backend-tests

Failed stage: Startup script launch (Fast) [❌]

Failure summary: The action failed due to Node.js version incompatibility: The build requires Node.js version ^20.17.0 || >=22.9.0 But the actual Node.js version installed is v20.13.1 This version mismatch caused npm installation to fail with error code EBADENGINE The failure occurred during the npm install and build process in the Docker build stage

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1695: #14 0.784 npm ERR! code EBADENGINE 1696: #14 0.785 npm ERR! engine Unsupported engine 1697: #14 0.786 npm ERR! engine Not compatible with your version of node/npm: npm@11.0.0 1698: #14 0.786 npm ERR! notsup Not compatible with your version of node/npm: npm@11.0.0 1699: #14 0.787 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} 1700: #14 0.787 npm ERR! notsup Actual: {"npm":"10.5.2","node":"v20.13.1"} 1701: #14 0.789 1702: #14 0.789 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-12-17T05_47_37_922Z-debug-0.log 1703: #14 ERROR: process "/bin/sh -c npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build" did not complete successfully: exit code: 1 1704: #12 [uwsgi backend-build 3/10] RUN apt-get update && apt-get install -y --no-install-recommends apt-utils libsasl2-dev libssl-dev netcat-traditional vim libldap2-dev libfuzzy-dev net-tools python3-psycopg2 git apache2-utils tshark && apt-get clean && rm -rf /var/lib/apt/lists/* && pip3 install --no-cache-dir --upgrade pip 1705: #12 1.495 Reading package lists... 1706: #12 1.984 Reading package lists... 1707: #12 2.404 Building dependency tree... 1708: #12 CANCELED 1709: failed to solve: process "/bin/sh -c npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build" did not complete successfully: exit code: 1 ... 1713: 0.785 npm ERR! engine Unsupported engine 1714: 0.786 npm ERR! engine Not compatible with your version of node/npm: npm@11.0.0 1715: 0.786 npm ERR! notsup Not compatible with your version of node/npm: npm@11.0.0 1716: 0.787 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} 1717: 0.787 npm ERR! notsup Actual: {"npm":"10.5.2","node":"v20.13.1"} 1718: 0.789 1719: 0.789 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-12-17T05_47_37_922Z-debug-0.log 1720: ------ 1721: ##[error]Process completed with exit code 17. 1722: ##[group]Run docker ps -a 1723: �[36;1mdocker ps -a�[0m 1724: �[36;1mdocker logs threatmatrix_uwsgi�[0m 1725: �[36;1mdocker logs threatmatrix_daphne�[0m 1726: shell: /usr/bin/bash -e {0} 1727: ##[endgroup] 1728: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1729: Error response from daemon: No such container: threatmatrix_uwsgi 1730: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[dependabot]

Superseded by #199.