Bump the github-actions group with 5 updates

Bumps the github-actions group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [step-security/harden-runner](https://github.com/step-security/harden-runner) | `2.6.1` | `2.7.0` |
| [bazelbuild/continuous-integration](https://github.com/bazelbuild/continuous-integration) | `9817b29fbb4b1fda32afb83b29574ec2d491feeb` | `b9b7f0dad8ab00a48cc262d1d38339a1dd11c7c5` |
| [redhat-plumbers-in-action/advanced-issue-labeler](https://github.com/redhat-plumbers-in-action/advanced-issue-labeler) | `2.0.3` | `3.0.0` |
| [actions/upload-artifact](https://github.com/actions/upload-artifact) | `4.3.0` | `4.3.1` |
| [github/codeql-action](https://github.com/github/codeql-action) | `3.23.2` | `3.24.6` |

Updates `step-security/harden-runner` from 2.6.1 to 2.7.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/step-security/harden-runner/releases">step-security/harden-runner's releases</a>.</em></p>
<blockquote>
<h2>v2.7.0</h2>
<h2>What's Changed</h2>
<p>Release 2.7.0 by <a href="https://github.com/varunsh-coder"><code>@​varunsh-coder</code></a> and <a href="https://github.com/h0x0er"><code>@​h0x0er</code></a> in <a href="https://redirect.github.com/step-security/harden-runner/pull/376">step-security/harden-runner#376</a>
This release:</p>
<ol>
<li>Updates the node runtime to node20</li>
<li>Adds capability to inspect outbound HTTPS traffic on GitHub-hosted and self-hosted VM runners</li>
</ol>
<p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2...v2.7.0">https://github.com/step-security/harden-runner/compare/v2...v2.7.0</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/step-security/harden-runner/commit/63c24ba6bd7ba022e95695ff85de572c04a18142"><code>63c24ba</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/376">#376</a> from step-security/rc-7</li>
<li><a href="https://github.com/step-security/harden-runner/commit/95691d3d1cfc1f403f673ccbe70465d7c4254108"><code>95691d3</code></a> Update dist</li>
<li><a href="https://github.com/step-security/harden-runner/commit/6339621ce7eb126e03da0cdd1e373bf4a86aa351"><code>6339621</code></a> Update to node20</li>
<li><a href="https://github.com/step-security/harden-runner/commit/4a63cdab7412f310777ba8aba65aafca4c1dd47f"><code>4a63cda</code></a> Add tls-inspection capability (<a href="https://redirect.github.com/step-security/harden-runner/issues/368">#368</a>)</li>
<li><a href="https://github.com/step-security/harden-runner/commit/dece11172ed6b762b5421b294513d628edad7f7d"><code>dece111</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/372">#372</a> from step-security/readme-update</li>
<li><a href="https://github.com/step-security/harden-runner/commit/1952f970702453e198ed55b40944bf4ffc0ad992"><code>1952f97</code></a> Updates</li>
<li><a href="https://github.com/step-security/harden-runner/commit/32f00ffb1b198fae962ae378ca876e01f367043f"><code>32f00ff</code></a> Update README.md</li>
<li><a href="https://github.com/step-security/harden-runner/commit/ea8b747819ff6d82907eb4018229f1a75c174697"><code>ea8b747</code></a> Publish test results (<a href="https://redirect.github.com/step-security/harden-runner/issues/363">#363</a>)</li>
<li><a href="https://github.com/step-security/harden-runner/commit/c0db65e1f64025718795419be8dbbf8c4050160f"><code>c0db65e</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/359">#359</a> from step-security/dependabot/github_actions/actions/...</li>
<li><a href="https://github.com/step-security/harden-runner/commit/4151c053ff9c3daff63c12b5175c94870ec73b53"><code>4151c05</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/361">#361</a> from step-security/dependabot/github_actions/step-sec...</li>
<li>Additional commits viewable in <a href="https://github.com/step-security/harden-runner/compare/v2.6.1...63c24ba6bd7ba022e95695ff85de572c04a18142">compare view</a></li>
</ul>
</details>
<br />

Updates `bazelbuild/continuous-integration` from 9817b29fbb4b1fda32afb83b29574ec2d491feeb to b9b7f0dad8ab00a48cc262d1d38339a1dd11c7c5
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/bazelbuild/continuous-integration/blob/master/docs/release-playbook.md">bazelbuild/continuous-integration's changelog</a>.</em></p>
<blockquote>
<h1>Bazel Release Playbook</h1>
<p>This is the guide to conducting a Bazel release. This is especially relevant for
release managers, but will be of interest to anyone who is curious about the
release process.</p>
<h2>Preface</h2>
<blockquote>
<p>For future reference and release managers - the release manager playbook should
be treated like an IKEA manual. That means: Do not try to be smart, optimize /
skip / reorder steps, otherwise chaos will ensue. Just follow it and the end
result will be.. well, a usable piece of furniture, or a Bazel release
(depending on the manual).</p>
<p>Like aviation and workplace safety regulations, the playbook is written in the
tears and blood of broken Bazelisks, pipelines, releases and Git branches.
Assume that every step is exactly there for a reason, even if it might not be
obvious. If you follow them to the letter, they are not error prone. Errors
have only happened in the past, when a release manager thought it's ok to
follow them by spirit instead. ;)</p>
<p>-- <a href="https://github.com/philwo"><code>@​philwo</code></a></p>
</blockquote>
<h2>One-time setup</h2>
<p>These steps only have to be performed once, ever.</p>
<ul>
<li>Make sure you are a member of the Bazel <a href="https://github.com/orgs/bazelbuild/teams/release-managers/members">Release Managers</a> team on GitHub.</li>
<li>Make sure you are a member of the Bazel <a href="https://buildkite.com/organizations/bazel-trusted/teams/release-managers/members">release-managers</a>
group on BuildKite.  If that link does not work for you, ask one of the Buildkite org admins to add you to
the group.</li>
<li>Set up github ssh key if you haven't already.
<ul>
<li><a href="https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/">https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/</a></li>
</ul>
</li>
<li>Generate a new identifier for Google's internal Git mirror: <a href="https://bazel.googlesource.com/new-password">https://bazel.googlesource.com/new-password</a> (and paste the code in your shell).</li>
<li>Log in to the Gerrit UI to create an account: <a href="[]
</ul>
<h2>Preparing a new release</h2>
<ol>
<li><a href="https://github.com/bazelbuild/bazel/milestones/new">Create a release blockers milestone</a> named &quot;X.Y.Z release blockers&quot; (case-sensitive), where we keep track of issues that must be resolved before the release goes out.
<ul>
<li>Set the (tentative) release date.</li>
<li>Add this description: <code>Issues that need to be resolved before the X.Y.Z release.</code>.</li>
<li>Refer to <a href="https://github.com/bazelbuild/bazel/milestone/38">this example</a></li>
</ul>
</li>
<li><a href="https://github.com/bazelbuild/bazel/issues/new?assignees=&amp;labels=release%2Cteam-OSS%2CP1%2Ctype%3A+process&amp;template=release.md&amp;title=Release+X.Y+-+%24MONTH+%24YEAR">Create a release tracking issue</a> to keep the community updated about the progress of the release. <a href="https://redirect.github.com/bazelbuild/bazel/issues/16159">See example</a>. Pin this issue.</li>
<li>Create the branch for the release. The branch should always be named <code>release-X.Y.Z</code> (the <code>.Z</code> part is important). Cherry-pick PRs will be sent against this branch.
<ul>
<li>The actual creation of the branch can be done via the GitHub UI or via the command line. For minor and patch releases, create the branch from the previous release tag, if possible. How we choose the base commit of the branch depends on the type of the release:</li>
<li>For patch releases (<code>X.Y.Z</code> where <code>Z&gt;0</code>), the base commit should simply be <code>X.Y.(Z-1)</code>.</li>
<li>For minor releases (<code>X.Y.0</code> where <code>Y&gt;0</code>), the base commit should typically be <code>X.(Y-1).&lt;current max Z&gt;</code>.</li>
<li>For major releases (<code>X.0.0</code>), the base commit is some &quot;healthy&quot; commit on the main branch.
<ul>
<li>This means that there's an extra step involved in preparing the release -- &quot;cutting&quot; the release branch, so to speak. For this, check the <a href="https://buildkite.com/bazel/bazel-with-downstream-projects-bazel">Bazel@HEAD+Downstream pipeline</a>. The branch cut should happen on a green commit there; if the pipeline is persistently red, work with the Green Team to resolve it first and delay the branch cut as needed.</li>
<li>A first release candidate should immediately be created after the release branch is created. See <a href="https://github.com/bazelbuild/continuous-integration/blob/master/docs/#create-a-release-candidate">create a release candidate</a> below.</li>
</ul>
</li>
</ul>
</li>
</ol>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/b9b7f0dad8ab00a48cc262d1d38339a1dd11c7c5"><code>b9b7f0d</code></a> Add bcr-pr-review-approver (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1887">#1887</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/dee7f0e141895b472bb668cb8f3952c5bb206aeb"><code>dee7f0e</code></a> Update bazel-postsubmit.yml</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/5e2c3baae2d2aca433af7796572851100f4493b2"><code>5e2c3ba</code></a> bazelci.py: fix get_modified_files (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1886">#1886</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/4dad9fa14aa8e5a918815d73bb58f66f88c8ec64"><code>4dad9fa</code></a> Use a fresh lockfile before building the distfile on centos</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/b230989533bea5884f2f6607ca733df5c7e9ed0f"><code>b230989</code></a> Strip top-level dir if the repo source archive is not from googlesource (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1885">#1885</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/82d8e775bc0e40995406f4b15e062cdebcf78db2"><code>82d8e77</code></a> Fix default branch in resolve_diffbase</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/38ab00bcb5d82917c7ac6444c6a2ecea2a5d3668"><code>38ab00b</code></a> Fix resolve_diffbase</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/86b979cab293adc2382aac7ff47ac7209b88a96e"><code>86b979c</code></a> bazel-diff: Make auto diffbase work (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1884">#1884</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/f3c70e8a99f35295049c54cb8c41da2b7e8afdcd"><code>f3c70e8</code></a> Pull docker images when building the Linux VM image (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1882">#1882</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/15b733e0e609a590e7bb0a517bfe7aaf169b912f"><code>15b733e</code></a> Support bazel-diff for GitHub PR presubmit (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1883">#1883</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/bazelbuild/continuous-integration/compare/9817b29fbb4b1fda32afb83b29574ec2d491feeb...b9b7f0dad8ab00a48cc262d1d38339a1dd11c7c5">compare view</a></li>
</ul>
</details>
<br />

Updates `redhat-plumbers-in-action/advanced-issue-labeler` from 2.0.3 to 3.0.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/releases">redhat-plumbers-in-action/advanced-issue-labeler's releases</a>.</em></p>
<blockquote>
<h2>v3.0.0</h2>
<h1>What's Changed</h1>
<h2>Breaking</h2>
<ul>
<li>Use zod for input validation :supervillain:  (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/275">#275</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
<li>Use octokit instead of probot :wastebasket:  (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/274">#274</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
</ul>
<h2>New</h2>
<ul>
<li>Add support for GitHub Enterprise :classical_building:  (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/277">#277</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
<li>Add option to set custom config file path (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/278">#278</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
</ul>
<h2>Bug Fixes</h2>
<ul>
<li>Use node16 for v2; the node20 will be used by v3 (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/281">#281</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
</ul>
<h2>Maintenance</h2>
<ul>
<li>Improve and update tests :test_tube:  (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/279">#279</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
</ul>
<h2>Dependency Updates</h2>
<ul>
<li>chore(deps): update dependency <code>@​vercel/ncc</code> to v0.38.1 (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/269">#269</a>) <a href="https://github.com/renovatebot"><code>@​renovatebot</code></a></li>
<li>chore(deps): update dependency eslint-plugin-prettier to v5.0.1 (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/270">#270</a>) <a href="https://github.com/renovatebot"><code>@​renovatebot</code></a></li>
<li>chore(deps): update dependency <code>@​types/node</code> to v18.18.9 (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/268">#268</a>) <a href="https://github.com/renovatebot"><code>@​renovatebot</code></a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/compare/v2.0.7...v3.0.0">https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/compare/v2.0.7...v3.0.0</a></p>
<h2>v2.1.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Use octokit instead of probot :wastebasket:  by <a href="https://github.com/jamacku"><code>@​jamacku</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/274">redhat-plumbers-in-action/advanced-issue-labeler#274</a></li>
<li>chore(deps): update dependency <code>@​types/node</code> to v18.18.9 by <a href="https://github.com/renovatebot"><code>@​renovatebot</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/268">redhat-plumbers-in-action/advanced-issue-labeler#268</a></li>
<li>chore(deps): update dependency eslint-plugin-prettier to v5.0.1 by <a href="https://github.com/renovatebot"><code>@​renovatebot</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/270">redhat-plumbers-in-action/advanced-issue-labeler#270</a></li>
<li>Use zod for input validation :supervillain:  by <a href="https://github.com/jamacku"><code>@​jamacku</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/275">redhat-plumbers-in-action/advanced-issue-labeler#275</a></li>
<li>chore(deps): update dependency <code>@​vercel/ncc</code> to v0.38.1 by <a href="https://github.com/renovatebot"><code>@​renovatebot</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/269">redhat-plumbers-in-action/advanced-issue-labeler#269</a></li>
<li>Add option to set custom config file path by <a href="https://github.com/jamacku"><code>@​jamacku</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/278">redhat-plumbers-in-action/advanced-issue-labeler#278</a></li>
<li>Improve and update tests :test_tube:  by <a href="https://github.com/jamacku"><code>@​jamacku</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/279">redhat-plumbers-in-action/advanced-issue-labeler#279</a></li>
<li>Add support for GitHub Enterprise :classical_building:  by <a href="https://github.com/jamacku"><code>@​jamacku</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/277">redhat-plumbers-in-action/advanced-issue-labeler#277</a></li>
<li>Use node16 for v2; the node20 will be used by v3 by <a href="https://github.com/jamacku"><code>@​jamacku</code></a> in <a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/pull/281">redhat-plumbers-in-action/advanced-issue-labeler#281</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/compare/v2.0.7...v2.1.0">https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/compare/v2.0.7...v2.1.0</a></p>
<h2>v2.0.6</h2>
<h1>What's Changed</h1>
<h2>Bug Fixes</h2>
<ul>
<li>Revert &quot;chore(deps): update actions-r-us/actions-tagger digest to 68b8860&quot; (<a href="https://redirect.github.com/redhat-plumbers-in-action/advanced-issue-labeler/issues/224">#224</a>) <a href="https://github.com/jamacku"><code>@​jamacku</code></a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/9e55064634b67244f7deb4211452b4a7217b93de"><code>9e55064</code></a> use node16 for v2</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/2c498657909ba61099fd5bc2d7922ad12a1ef06b"><code>2c49865</code></a> feat: add support for GitHub Enterprise</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/fd1e8262fb4378c61267b339893a4faeb7056f3e"><code>fd1e826</code></a> build: update <code>dist/</code> files and <code>yarn.lock</code></li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/5d9945a97d466af38be6ed07b69d9dd36cae2281"><code>5d9945a</code></a> test: update unit tests of config/policy</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/c75d2363113e57e01280a7847e87d800351085f5"><code>c75d236</code></a> doc: update Note/Warning GitHub Markdown</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/22df69361cc8fcf26bb8a29bd96ed9bf46de72fd"><code>22df693</code></a> drop <code>codecov.yml</code> file</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/46baf0f97a89dc9d4187e7306f65cbe207745266"><code>46baf0f</code></a> feat: add option to set custom config file path</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/2952a1d4c0ad02119712845627effbfcd14730b0"><code>2952a1d</code></a> chore(deps): update dependency <code>@​vercel/ncc</code> to v0.38.1</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/a0c8e0129e8d17385af40823024c33f1300c0e5f"><code>a0c8e01</code></a> refactor: use zod instead of class-validator</li>
<li><a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/commit/99a9075109da0d9e735beefa2ada4ad079f10167"><code>99a9075</code></a> add input hardening check using <code>@​total-typescript/ts-reset</code></li>
<li>Additional commits viewable in <a href="https://github.com/redhat-plumbers-in-action/advanced-issue-labeler/compare/6ee6fddfd744ee26b977e6a0436916f256896971...9e55064634b67244f7deb4211452b4a7217b93de">compare view</a></li>
</ul>
</details>
<br />

Updates `actions/upload-artifact` from 4.3.0 to 4.3.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/upload-artifact/releases">actions/upload-artifact's releases</a>.</em></p>
<blockquote>
<h2>v4.3.1</h2>
<ul>
<li>Bump <code>@​actions/artifacts</code> to latest version to include <a href="https://redirect.github.com/actions/toolkit/pull/1648">updated GHES host check</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/upload-artifact/commit/5d5d22a31266ced268874388b861e4b58bb5c2f3"><code>5d5d22a</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/515">#515</a> from actions/eggyhead/update-artifact-v2.1.1</li>
<li><a href="https://github.com/actions/upload-artifact/commit/f1e993d9663a03508e7fc0370c744c4b963f0044"><code>f1e993d</code></a> update artifact license</li>
<li><a href="https://github.com/actions/upload-artifact/commit/4881bfd3f27855c63733d8cfff17721cc0ad611f"><code>4881bfd</code></a> updating dist:</li>
<li><a href="https://github.com/actions/upload-artifact/commit/a30777e2653648a0a7bbd3efb5c96ef9131b96cc"><code>a30777e</code></a> <a href="https://github.com/eggyhead"><code>@​eggyhead</code></a></li>
<li><a href="https://github.com/actions/upload-artifact/commit/3a8048248f2f288c271830f8ecf2a1c5d8eb0e9a"><code>3a80482</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/511">#511</a> from actions/robherley/migration-docs-typo</li>
<li><a href="https://github.com/actions/upload-artifact/commit/9d63e3f2f81d9dc4e13d83fc330408f8a94b79d1"><code>9d63e3f</code></a> Merge branch 'main' into robherley/migration-docs-typo</li>
<li><a href="https://github.com/actions/upload-artifact/commit/dfa1ab292d2fdd78d056187f11c568c16ab53de9"><code>dfa1ab2</code></a> fix typo with v3 artifact downloads in migration guide</li>
<li><a href="https://github.com/actions/upload-artifact/commit/d00351bf698398c17253d21cf8f90e57a344e14b"><code>d00351b</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/509">#509</a> from markmssd/patch-1</li>
<li><a href="https://github.com/actions/upload-artifact/commit/707f5a7b71e0fb01c5df1e16e9679a3292606ef2"><code>707f5a7</code></a> Update limitation of <code>10</code> artifacts upload to <code>500</code></li>
<li>See full diff in <a href="https://github.com/actions/upload-artifact/compare/26f96dfa697d77e81fd5907df203aa23a56210a8...5d5d22a31266ced268874388b861e4b58bb5c2f3">compare view</a></li>
</ul>
</details>
<br />

Updates `github/codeql-action` from 3.23.2 to 3.24.6
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action's changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p>
<p>Note that the only difference between <code>v2</code> and <code>v3</code> of the CodeQL Action is the node version they support, with <code>v3</code> running on node 20 while we continue to release <code>v2</code> to support running on node 16. For example <code>3.22.11</code> was the first <code>v3</code> release and is functionally identical to <code>2.22.11</code>. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.</p>
<h2>[UNRELEASED]</h2>
<p>No user facing changes.</p>
<h2>3.24.6 - 29 Feb 2024</h2>
<p>No user facing changes.</p>
<h2>3.24.5 - 23 Feb 2024</h2>
<ul>
<li>Update default CodeQL bundle version to 2.16.3. <a href="https://redirect.github.com/github/codeql-action/pull/2156">#2156</a></li>
</ul>
<h2>3.24.4 - 21 Feb 2024</h2>
<ul>
<li>Fix an issue where an existing, but empty, <code>/sys/fs/cgroup/cpuset.cpus</code> file always resulted in a single-threaded run. <a href="https://redirect.github.com/github/codeql-action/pull/2151">#2151</a></li>
</ul>
<h2>3.24.3 - 15 Feb 2024</h2>
<ul>
<li>Fix an issue where the CodeQL Action would fail to load a configuration specified by the <code>config</code> input to the <code>init</code> Action. <a href="https://redirect.github.com/github/codeql-action/pull/2147">#2147</a></li>
</ul>
<h2>3.24.2 - 15 Feb 2024</h2>
<ul>
<li>Enable improved multi-threaded performance on larger runners for GitHub Enterprise Server users. This feature is already available to GitHub.com users. <a href="https://redirect.github.com/github/codeql-action/pull/2141">#2141</a></li>
</ul>
<h2>3.24.1 - 13 Feb 2024</h2>
<ul>
<li>Update default CodeQL bundle version to 2.16.2. <a href="https://redirect.github.com/github/codeql-action/pull/2124">#2124</a></li>
<li>The CodeQL action no longer fails if it can't write to the telemetry api endpoint. <a href="https://redirect.github.com/github/codeql-action/pull/2121">#2121</a></li>
</ul>
<h2>3.24.0 - 02 Feb 2024</h2>
<ul>
<li>CodeQL Python analysis will no longer install dependencies on GitHub Enterprise Server, as is already the case for GitHub.com. See <a href="https://github.com/github/codeql-action/blob/main/#3230---08-jan-2024">release notes for 3.23.0</a> for more details. <a href="https://redirect.github.com/github/codeql-action/pull/2106">#2106</a></li>
</ul>
<h2>3.23.2 - 26 Jan 2024</h2>
<ul>
<li>On Linux, the maximum possible value for the <code>--threads</code> option now respects the CPU count as specified in <code>cgroup</code> files to more accurately reflect the number of available cores when running in containers. <a href="https://redirect.github.com/github/codeql-action/pull/2083">#2083</a></li>
<li>Update default CodeQL bundle version to 2.16.1. <a href="https://redirect.github.com/github/codeql-action/pull/2096">#2096</a></li>
</ul>
<h2>3.23.1 - 17 Jan 2024</h2>
<ul>
<li>Update default CodeQL bundle version to 2.16.0. <a href="https://redirect.github.com/github/codeql-action/pull/2073">#2073</a></li>
<li>Change the retention period for uploaded debug artifacts to 7 days. Previously, this was whatever the repository default was. <a href="https://redirect.github.com/github/codeql-action/pull/2079">#2079</a></li>
</ul>
<h2>3.23.0 - 08 Jan 2024</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/github/codeql-action/commit/8a470fddafa5cbb6266ee11b37ef4d8aae19c571"><code>8a470fd</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2176">#2176</a> from github/update-v3.24.6-158d0780d</li>
<li><a href="https://github.com/github/codeql-action/commit/d59eafb69b1bbf6ebc4592895da945a4cc588806"><code>d59eafb</code></a> Update changelog for v3.24.6</li>
<li><a href="https://github.com/github/codeql-action/commit/158d0780dc10ed5108b9fb567ea80a54c245dd67"><code>158d078</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2175">#2175</a> from github/henrymercer/fix-languages-init-success</li>
<li><a href="https://github.com/github/codeql-action/commit/2307ff547f1c8a003d306eede350ccff46e0e65d"><code>2307ff5</code></a> Add <code>languages</code> and <code>build_mode</code> to <code>init</code> <code>success</code> status report</li>
<li><a href="https://github.com/github/codeql-action/commit/ccd3f0254505d3abf6b996df24b8cc9a0d77c98f"><code>ccd3f02</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2173">#2173</a> from github/henrymercer/mark-third-party-limits-erro...</li>
<li><a href="https://github.com/github/codeql-action/commit/c0917251d4d0392e762284c11e2c9c1b82195af1"><code>c091725</code></a> Refactoring: Convert <code>ActionName</code> to enum</li>
<li><a href="https://github.com/github/codeql-action/commit/e12a8cc5eb90431cfed6096ac78c48448b5cf331"><code>e12a8cc</code></a> Use <code>isFirstPartyAnalysis</code> for a stronger check</li>
<li><a href="https://github.com/github/codeql-action/commit/888ab31e3edfe95e943195e117426658cc6a3802"><code>888ab31</code></a> Mark third-party SARIF limits errors as configuration errors</li>
<li><a href="https://github.com/github/codeql-action/commit/bd56a05133734527a524799b550f71febf4597b9"><code>bd56a05</code></a> Rename <code>InvalidRequestError</code> to <code>InvalidSarifUploadError</code></li>
<li><a href="https://github.com/github/codeql-action/commit/7bde9061b48b68e993ca909411613cf15bd12708"><code>7bde906</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2172">#2172</a> from github/henrymercer/fix-readme-typos</li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/b7bf0a3ed3ecfa44160715d7c442788f65f0f923...8a470fddafa5cbb6266ee11b37ef4d8aae19c571">compare view</a></li>
</ul>
</details>
<br />

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions

</details>

Closes #21536.

PiperOrigin-RevId: 613191158
Change-Id: I872a2f7eb3d7a19efa0ff0346aa990626bfa0142
4 files changed
tree: 461e9eced4eaee535cb7886a1d0532d858d6a79c
  1. .bazelci/
  2. .github/
  3. examples/
  4. scripts/
  5. site/
  6. src/
  7. third_party/
  8. tools/
  9. .bazelrc
  10. .bazelversion
  11. .gitattributes
  12. .gitignore
  13. AUTHORS
  14. bazel_downloader.cfg
  15. BUILD
  16. CHANGELOG.md
  17. CODE_OF_CONDUCT.md
  18. CODEOWNERS
  19. combine_distfiles.py
  20. combine_distfiles_to_tar.sh
  21. compile.sh
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. distdir.bzl
  25. extensions.bzl
  26. LICENSE
  27. maven_install.json
  28. MODULE.bazel
  29. MODULE.bazel.lock
  30. rbe_extension.bzl
  31. README.md
  32. repositories.bzl
  33. requirements.txt
  34. SECURITY.md
  35. WORKSPACE
  36. WORKSPACE.bzlmod
  37. workspace_deps.bzl
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status