Skip to content

Update all non-major github action - #757

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-github-action
Open

Update all non-major github action#757
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-github-action

Conversation

@renovate

@renovate renovate Bot commented Sep 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
github/codeql-action action minor v4.38.0 → v4.39.1
zeebe-io/backport-action action minor v4.6.0 → v4.7.0

Release Notes

github/codeql-action

v4.39.1

Compare Source

v4.39.0

Compare Source

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #​4205
  • The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #​4148
  • Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #​4206
  • The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #​4198

v4.38.3

Compare Source

  • Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4188
  • Update default CodeQL bundle version to 2.27.2. #​4203
  • Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #​4184

v4.38.2

Compare Source

v4.38.1

Compare Source

  • The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #​4146
zeebe-io/backport-action

v4.7.0: Backport-action v4.7.0

Compare Source

What's Changed

Thanks to a great contribution by @​lexfrei, backports no longer fail when the target branch already contains some of the changes, for example if a specific commit was already manually cherry-picked, or on a re-run. Previously, git reported the empty cherry-pick as a conflict, so the backport failed (or opened a draft PR with conflict_resolution: draft_commit_conflicts).

Now the action skips those commits:

  • Some commits already on the target: the backport PR is created as usual. The comment on the original pull request mentions the skipped commits, and a comment on the backport PR lists them.
  • All commits already on the target: there's nothing to backport, so no PR is created. The target is skipped, just like when its backport PR already exists, and doesn't count as a failure in was_successful.

With comment_style: summary, that looks like this:

Target Status
stable/8.7 ✅ Created #​612 — 1 commit skipped (target already contains changes)
stable/8.6 ➖ Skipped (target already contains changes)

No configuration needed to enable this. This is a bug fix released in a new minor version to avoid surprising users with new behavior.

New Contributors

Updated dependencies

Full Changelog: korthout/backport-action@v4.6.1...v4.7.0

v4.6.1: Backport-action v4.6.1

Compare Source

What's Changed

Dependency updates only.

Updated dependencies
Maintenance changes

Full Changelog: korthout/backport-action@v4.6.0...v4.6.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 requested a review from ulucinar as a code owner September 17, 2026 17:35
@renovate renovate Bot changed the title Update jlumbroso/free-disk-space action to v1.3.2 Update all non-major github action Sep 18, 2026
@renovate
renovate Bot force-pushed the renovate/all-non-major-github-action branch 3 times, most recently from e24f907 to b02fadb Compare September 24, 2026 23:30
@renovate
renovate Bot force-pushed the renovate/all-non-major-github-action branch 2 times, most recently from 07a83c5 to 1269140 Compare October 1, 2026 15:27
@renovate
renovate Bot force-pushed the renovate/all-non-major-github-action branch 3 times, most recently from 3046435 to 1ccf65a Compare October 15, 2026 12:48
@renovate
renovate Bot force-pushed the renovate/all-non-major-github-action branch 2 times, most recently from 9e3ad7c to 7f2ce23 Compare October 21, 2026 21:29
@renovate
renovate Bot force-pushed the renovate/all-non-major-github-action branch from 7f2ce23 to d478c58 Compare October 29, 2026 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ulucinar ulucinar Awaiting requested review from ulucinar ulucinar is a code owner
@sergenyalcin sergenyalcin Awaiting requested review from sergenyalcin sergenyalcin is a code owner
@erhancagirici erhancagirici Awaiting requested review from erhancagirici erhancagirici is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

automated renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants