Skip to content

fix(deps): update non-major-updates (feature/beta-release)#734

Merged
Wikid82 merged 1 commit intofeature/beta-releasefrom
renovate/feature/beta-release-non-major-updates
Feb 20, 2026
Merged

fix(deps): update non-major-updates (feature/beta-release)#734
Wikid82 merged 1 commit intofeature/beta-releasefrom
renovate/feature/beta-release-non-major-updates

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 20, 2026

This PR contains the following updates:

Package Type Update Change Age Confidence
github/codeql-action (changelog) action digest 9e907b589a39a4
github/codeql-action action patch v4.32.3v4.32.4 age confidence
github/codeql-action action digest 5e7a52f710e294
i18next (source) dependencies patch ^25.8.11^25.8.13 age confidence

Release Notes

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

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
i18next/i18next (i18next)

v25.8.13

Compare Source

  • improve support notice shown logic

Configuration

📅 Schedule: 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.

@Wikid82 Wikid82 merged commit 3a3c06a into feature/beta-release Feb 20, 2026
26 checks passed
@Wikid82 Wikid82 deleted the renovate/feature/beta-release-non-major-updates branch February 20, 2026 19:27
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@github-actions
Copy link
Contributor

✅ Supply Chain Verification Results

PASSED

📦 SBOM Summary

  • Components: 1671

🔍 Vulnerability Scan

Severity Count
🔴 Critical 0
🟠 High 0
🟡 Medium 9
🟢 Low 4
Total 13

📎 Artifacts

  • SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

Generated by Supply Chain Verification workflow • View Details

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant