Skip to content

chore(deps): update workflows#174

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/workflows
Open

chore(deps): update workflows#174
renovate[bot] wants to merge 1 commit intomainfrom
renovate/workflows

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jan 26, 2026 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/setup-node action minor v6.2.0 → v6.3.0
actions/upload-artifact action patch v7.0.0 → v7.0.1
astral-sh/ruff-action action minor v3.5.1 → v3.6.1
github/codeql-action action minor v4.31.11 → v4.35.1
peter-evans/create-pull-request action patch v8.1.0 → v8.1.1

Release Notes

actions/setup-node (actions/setup-node)

v6.3.0

Compare Source

What's Changed

Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:
Bug fixes:

New Contributors

Full Changelog: actions/setup-node@v6...v6.3.0

actions/upload-artifact (actions/upload-artifact)

v7.0.1

Compare Source

astral-sh/ruff-action (astral-sh/ruff-action)

v3.6.1: 🌈 fix automatic minor tag updates

Compare Source

Changes

This is just a bugfix release for the release process

🧰 Maintenance

v3.6.0: 🌈 search for pyproject.toml in parent dirs

Compare Source

Changes

This release brings some bug fixes like

  • support for hashes in requirement.txt files
  • ignoring environment markers in version specifiers like "ruff~=0.13 ; python_version >= '3.11'" to prevent them from breaking the version resolver. If you have a usecase for needing the environment markers to derive the correct ruff version this action should use please add your voice to #​256

In case no pyproject.toml is in the configured src this action now also walks up the directory tree to search for it, just like the "normal" ruff does. This is limited to the current workspace to prevent this action from trying to access private data outside the GitHub Actions runner.

EDIT: Oh I forgot to mention that the error matcher now properly detects invalid formatting and displays the correct line number etc in the GitHub UI.

🐛 Bug fixes

🚀 Enhancements

🧰 Maintenance

⬆️ Dependency updates

github/codeql-action (github/codeql-action)

v4.35.1

Compare Source

v4.35.0

Compare Source

v4.34.1

Compare Source

  • Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #​3762

v4.34.0

Compare Source

  • Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #​3569
  • We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #​3584
  • Update default CodeQL bundle version to 2.25.0. #​3585

v4.33.0

Compare Source

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #​3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

  • Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #​3557

  • The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #​3559

  • Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #​3563

  • Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #​3564

  • A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #​3570

v4.32.6

Compare Source

v4.32.5

Compare Source

  • Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #​3507
  • Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #​3487
  • The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #​3515
  • Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #​3516
  • Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #​3498
  • Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #​3512
  • The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #​3503, #​3504

v4.32.4

Compare Source

  • Update default CodeQL bundle version to 2.24.2. #​3493
  • Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #​3473
  • When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #​3486
  • Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #​3485
  • Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #​3484

v4.32.3

Compare Source

  • Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #​3466

v4.32.2

Compare Source

v4.32.1

Compare Source

  • A warning is now shown in Default Setup workflow logs if a private package registry is configured using a GitHub Personal Access Token (PAT), but no username is configured. #​3422
  • Fixed a bug which caused the CodeQL Action to fail when repository properties cannot successfully be retrieved. #​3421

v4.32.0

Compare Source

peter-evans/create-pull-request (peter-evans/create-pull-request)

v8.1.1: Create Pull Request v8.1.1

Compare Source

What's Changed

Full Changelog: peter-evans/create-pull-request@v8.1.0...v8.1.1

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/workflows branch from 6a55397 to 7af4ec9 Compare January 30, 2026 09:35
@renovate renovate bot changed the title chore(deps): update github/codeql-action action to v4.32.0 chore(deps): update workflows Jan 30, 2026
@renovate renovate bot force-pushed the renovate/workflows branch 3 times, most recently from 33056b2 to a06019c Compare February 5, 2026 20:38
@renovate renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 4ec5086 to 3820184 Compare February 13, 2026 14:12
@renovate renovate bot force-pushed the renovate/workflows branch from 3820184 to b86ffc0 Compare February 20, 2026 18:05
@renovate renovate bot force-pushed the renovate/workflows branch 4 times, most recently from cdc9e55 to cf95253 Compare March 5, 2026 22:13
@renovate renovate bot force-pushed the renovate/workflows branch 3 times, most recently from d95021c to 514afa6 Compare March 20, 2026 20:47
@renovate renovate bot force-pushed the renovate/workflows branch 3 times, most recently from 4953315 to 0caba9a Compare March 27, 2026 17:06
@renovate renovate bot force-pushed the renovate/workflows branch 2 times, most recently from c6f9d35 to 1776a73 Compare April 10, 2026 17:38
@renovate renovate bot force-pushed the renovate/workflows branch from 1776a73 to 63eaa68 Compare April 10, 2026 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants