[dependabot]

Bumps github/codeql-action/upload-sarif from 3.39.3 to 4.39.3.

Release notes

Sourced from github/codeql-action/upload-sarif's releases.

v4.39.3

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

v4.39.1

• Update default CodeQL bundle version to 2.27.3. #4256

v4.39.0

• 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

• 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

• Update default CodeQL bundle version to 2.27.1. #4160

v4.38.1

• 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

v4.38.0

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
• Update default CodeQL bundle version to 2.27.0. #4129

v4.37.9

• Update default CodeQL bundle version to 2.26.4. #4106

v4.37.8

No user facing changes.

v4.37.7

• Update default CodeQL bundle version to 2.26.3. #4085

v4.37.6

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

... (truncated)

Changelog

Sourced from github/codeql-action/upload-sarif's changelog.

CodeQL Action Changelog

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

[UNRELEASED]

No user facing changes.

4.39.3 - 04 Nov 2026

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• 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

4.38.3 - 08 Oct 2026

• 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

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• 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

4.38.0 - 09 Sept 2026

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
• Update default CodeQL bundle version to 2.27.0. #4129

... (truncated)

Commits

• 3062620 Rebuild
• eb1e5bd Update changelog and version after v4.39.2
• 1fc58d0 Merge pull request #4286 from github/update-v4.39.2-c05042115
• dc4b73f Bump node-forge from 1.4.0 to 1.4.1
• 3b22011 Bump glob from 13.0.6 to 14.0.3 in /pr-checks
• d998481 Update changelog for v4.39.2
• 0d5ac7a Merge pull request #4285 from github/henrymercer/automated-change-notes
• 70417cd Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• See full diff 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 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)

[dependabot]

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

🤖 DevShelf AI-Driven PR Optimization & Tagging

Automated Heuristic Analyzer • Add GEMINI_API_KEY for LLM enhancement.

📦 Resource: Open-Meteo

• Target File: shelf/apis.json
• Suggested Category: Weather & Climate.json
• Recommended Tags: [100% Free Tier] [No Auth Required]

📝 Description Refinement

• Original: "Free weather forecast API for commercial and non-commercial use with hourly forecasts and historical weather data."
• ✨ Suggested: "Free weather forecast API for commercial and non-commercial use with hourly forecasts and historical weather data."

📋 Ready-to-Merge JSON Block

{
  "name": "Open-Meteo",
  "url": "https://open-meteo.com",
  "category": "Weather & Climate",
  "description": "Free weather forecast API for commercial and non-commercial use with hourly forecasts and historical weather data.",
  "auth": "No Key",
  "cors": "Yes",
  "rateLimit": "10,000 req/day",
  "https": true,
  "statusTags": [
    "[100% Free Tier]",
    "[No Auth Required]"
  ],
  "section": "Weather & Climate"
}

---

💡 Contributors can copy the JSON block above directly into their PR to ensure pristine catalog formatting.

[github-actions]

🤖 DevShelf AI-Driven PR Optimization & Tagging

Automated Heuristic Analyzer • Add GEMINI_API_KEY for LLM enhancement.

📦 Resource: Open-Meteo

• Target File: shelf/apis.json
• Suggested Category: Weather & Climate.json
• Recommended Tags: [100% Free Tier] [No Auth Required]

📝 Description Refinement

• Original: "Free weather forecast API for commercial and non-commercial use with hourly forecasts and historical weather data."
• ✨ Suggested: "Free weather forecast API for commercial and non-commercial use with hourly forecasts and historical weather data."

📋 Ready-to-Merge JSON Block

{
  "name": "Open-Meteo",
  "url": "https://open-meteo.com",
  "category": "Weather & Climate",
  "description": "Free weather forecast API for commercial and non-commercial use with hourly forecasts and historical weather data.",
  "auth": "No Key",
  "cors": "Yes",
  "rateLimit": "10,000 req/day",
  "https": true,
  "statusTags": [
    "[100% Free Tier]",
    "[No Auth Required]"
  ],
  "section": "Weather & Climate"
}

---

💡 Contributors can copy the JSON block above directly into their PR to ensure pristine catalog formatting.

[github-actions]

🚀 Congratulations @dependabot[bot]! Your tool is officially LIVE on DevShelf! 🎉

Your submission of your project has passed all schema, duplicate, and endpoint integrity audits and is now merged into main!

🌐 Permanent Live Listing

Your project has a dedicated, high-ranking SEO landing page with verified zero-paywall status and machine-readable JSON-LD grounding:
👉 View your project on DevShelf

---

⚡ Want 10x More Developer Discovery? Feature Your Tool

DevShelf reaches thousands of technical founders, engineers, and AI developers every week across the Web, CLI (devshelf search), and MCP agents.

As a verified contributor, unlock the Featured Sponsor Tier ($49/mo):

• 📌 Pinned Top Search Ranking: Always appear first when developers search your category.
• 🎖️ Gold 'Verified Sponsor' Badge: Stand out with trust verification on web & CLI results.
• 📬 DevShelf Digest Blast: Featured highlight in our weekly newsletter and RSS feed.

💳 Upgrade to Verified Sponsor via Dodo Payments ($49/mo)
(Or view all patron tiers & invoice options on the DevShelf Sponsor Portal)

---

🏷️ Add the Official "DevShelf Verified" Backlink Badge

Show users that your project is community-verified with zero paywalls by adding an official badge to your README.md:

Style 1: Verified Green Pill (Recommended)

[![DevShelf Verified](https://ritualdev.in/api/v1/badges/verified/.svg)](https://ritualdev.in/devshelf)

Style 2: Flat Shield Badge

[![Featured on DevShelf](https://ritualdev.in/api/v1/badges/featured.svg)](https://ritualdev.in/devshelf)

🎨 Open README Badge Studio for HTML/RST and Rich Cards

---

📢 Amplify & Get Discovered

• 🐦 Click here to share the news on X / Twitter to get amplified by @RitualDevLab
• ⭐ Give RitualDev-Lab/DevShelf a star on GitHub to help more developers discover great open-source tools!

Welcome to the community! 🤝