| commit | c654be5f146773e3e4c0ef6f12cbde2cc2c11162 | [log] [tgz] |
|---|---|---|
| author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Wed Feb 07 02:04:03 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 07 02:10:01 2024 -0800 |
| tree | b7145956080e0965ca96871a31144de6fd341f39 | |
| parent | 6922aea52cf1908f9e26b5d6bbe40f7de774f921 [diff] |
Bump the github-actions group with 4 updates Bumps the github-actions group with 4 updates: [step-security/harden-runner](https://github.com/step-security/harden-runner), [bazelbuild/continuous-integration](https://github.com/bazelbuild/continuous-integration), [actions/upload-artifact](https://github.com/actions/upload-artifact) and [github/codeql-action](https://github.com/github/codeql-action). 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/eb238b55efaa70779f274895e782ed17c84f2895...63c24ba6bd7ba022e95695ff85de572c04a18142">compare view</a></li> </ul> </details> <br /> Updates `bazelbuild/continuous-integration` from d646a2d9a98e699bdba517276cf0e16cfff0c62c to 9817b29fbb4b1fda32afb83b29574ec2d491feeb <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 "X.Y.Z release blockers" (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=&labels=release%2Cteam-OSS%2CP1%2Ctype%3A+process&template=release.md&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>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>0</code>), the base commit should typically be <code>X.(Y-1).<current max Z></code>.</li> <li>For major releases (<code>X.0.0</code>), the base commit is some "healthy" commit on the main branch. <ul> <li>This means that there's an extra step involved in preparing the release -- "cutting" 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/9817b29fbb4b1fda32afb83b29574ec2d491feeb"><code>9817b29</code></a> Avoid broken pipe issue during Linux image creation</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/e260ecac883f1420f0d55152f57b6527e020d98b"><code>e260eca</code></a> Add bazel version in the BCR presubmit job label (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1864">#1864</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/1616315b3d1f3f37b435f79d0327a1aed2f7977f"><code>1616315</code></a> Remove non-hermetic build tools (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1862">#1862</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/e2b6b06c39bba496a44b4aa0de4ce8225f138f7e"><code>e2b6b06</code></a> Disable rules_jsonnet in Downstream CI (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1863">#1863</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/3358b926c188162cbc8ab477d4882c87a1471222"><code>3358b92</code></a> Disable rules_cc and Flogger in Downstream CI (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1861">#1861</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/e1ca35d0980ef1fc0e83cdc8e01a7483868fd22a"><code>e1ca35d</code></a> Read script from HEAD when --script is set (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1860">#1860</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/9667e8d14136922a5f3e9184832ca3c1567c2acb"><code>9667e8d</code></a> Update release comms (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1859">#1859</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/b15a6ec9d0f103d440f6d4db48cc71097dc7d967"><code>b15a6ec</code></a> Revert "Duplicate task configs to test all supported Bazel LTS releases (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1858">#1858</a>)"</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/b4d5bc4c506313f228a297a5bf6fe30be6fba558"><code>b4d5bc4</code></a> Duplicate task configs to test all supported Bazel LTS releases (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/1858">#1858</a>)</li> <li><a href="https://github.com/bazelbuild/continuous-integration/commit/83e4a7f2d37759434dbd219b08104a79fd8ec291"><code>83e4a7f</code></a> Prevent running bazel-diff from updating Bazel lockfile</li> <li>Additional commits viewable in <a href="https://github.com/bazelbuild/continuous-integration/compare/d646a2d9a98e699bdba517276cf0e16cfff0c62c...9817b29fbb4b1fda32afb83b29574ec2d491feeb">compare view</a></li> </ul> </details> <br /> Updates `actions/upload-artifact` from 4.0.0 to 4.3.0 <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.0</h2> <h2>What's Changed</h2> <ul> <li>Reorganize upload code in prep for merge logic & add more tests by <a href="https://github.com/robherley"><code>@robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/504">actions/upload-artifact#504</a></li> <li>Add sub-action to merge artifacts by <a href="https://github.com/robherley"><code>@robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/505">actions/upload-artifact#505</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4...v4.3.0">https://github.com/actions/upload-artifact/compare/v4...v4.3.0</a></p> <h2>v4.2.0</h2> <h2>What's Changed</h2> <ul> <li>Ability to overwrite an Artifact by <a href="https://github.com/robherley"><code>@robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/501">actions/upload-artifact#501</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4...v4.2.0">https://github.com/actions/upload-artifact/compare/v4...v4.2.0</a></p> <h2>v4.1.0</h2> <h2>What's Changed</h2> <ul> <li>Add migrations docs by <a href="https://github.com/robherley"><code>@robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/482">actions/upload-artifact#482</a></li> <li>Update README.md by <a href="https://github.com/samuelwine"><code>@samuelwine</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/492">actions/upload-artifact#492</a></li> <li>Support artifact-url output by <a href="https://github.com/konradpabjan"><code>@konradpabjan</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/496">actions/upload-artifact#496</a></li> <li>Update readme to reflect new 500 artifact per job limit by <a href="https://github.com/robherley"><code>@robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/497">actions/upload-artifact#497</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/samuelwine"><code>@samuelwine</code></a> made their first contribution in <a href="https://redirect.github.com/actions/upload-artifact/pull/492">actions/upload-artifact#492</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4...v4.1.0">https://github.com/actions/upload-artifact/compare/v4...v4.1.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/upload-artifact/commit/26f96dfa697d77e81fd5907df203aa23a56210a8"><code>26f96df</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/505">#505</a> from actions/robherley/merge-artifacts</li> <li><a href="https://github.com/actions/upload-artifact/commit/530ed2c9b8e7b46db7acf98b7e543836a040586e"><code>530ed2c</code></a> use correct artifact name in test</li> <li><a href="https://github.com/actions/upload-artifact/commit/53ef6987b3562a24090358abb83a07f2c2bfec26"><code>53ef698</code></a> add additional integration test for merge all behavior</li> <li><a href="https://github.com/actions/upload-artifact/commit/90b0f8eed8fd7a9e62025ff26858a0f618d12b53"><code>90b0f8e</code></a> add workflow to test merging</li> <li><a href="https://github.com/actions/upload-artifact/commit/199a58f54fa418c391917374e9d11f5a5e618ae9"><code>199a58f</code></a> more docs</li> <li><a href="https://github.com/actions/upload-artifact/commit/3f353f9d9ee7e6a8313bfb227f44aa283e6832c9"><code>3f353f9</code></a> ncc</li> <li><a href="https://github.com/actions/upload-artifact/commit/997fffa3558d08f16f0c12036708e1ce7c0a7430"><code>997fffa</code></a> add merge artifact sub-action</li> <li><a href="https://github.com/actions/upload-artifact/commit/52899c8c02604e1c6c9ea56b52ead4671321bd05"><code>52899c8</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/504">#504</a> from actions/robherley/reorganize</li> <li><a href="https://github.com/actions/upload-artifact/commit/da58a3f7b2ea3d2db018d82fe856b2d4b297de35"><code>da58a3f</code></a> ncc</li> <li><a href="https://github.com/actions/upload-artifact/commit/1f64adb8530b493d492e8084db08a55f3856e94e"><code>1f64adb</code></a> fix import</li> <li>Additional commits viewable in <a href="https://github.com/actions/upload-artifact/compare/c7d193f32edcb7bfad88892161225aeda64e9392...26f96dfa697d77e81fd5907df203aa23a56210a8">compare view</a></li> </ul> </details> <br /> Updates `github/codeql-action` from 3.22.12 to 3.23.2 <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.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> <ul> <li>We are rolling out a feature in January 2024 that will disable Python dependency installation by default for all users. This improves the speed of analysis while having only a very minor impact on results. You can override this behavior by setting <code>CODEQL_ACTION_DISABLE_PYTHON_DEPENDENCY_INSTALLATION=false</code> in your workflow, however we plan to remove this ability in future versions of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/2031">#2031</a></li> <li>The CodeQL Action now requires CodeQL version 2.11.6 or later. For more information, see <a href="https://github.com/github/codeql-action/blob/main/#2227---16-nov-2023">the corresponding changelog entry for CodeQL Action version 2.22.7</a>. <a href="https://redirect.github.com/github/codeql-action/pull/2009">#2009</a></li> </ul> <h2>3.22.12 - 22 Dec 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.5. <a href="https://redirect.github.com/github/codeql-action/pull/2047">#2047</a></li> </ul> <h2>3.22.11 - 13 Dec 2023</h2> <ul> <li>[v3+ only] The CodeQL Action now runs on Node.js v20. <a href="https://redirect.github.com/github/codeql-action/pull/2006">#2006</a></li> </ul> <h2>2.22.10 - 12 Dec 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.4. <a href="https://redirect.github.com/github/codeql-action/pull/2016">#2016</a></li> </ul> <h2>2.22.9 - 07 Dec 2023</h2> <p>No user facing changes.</p> <h2>2.22.8 - 23 Nov 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.3. <a href="https://redirect.github.com/github/codeql-action/pull/2001">#2001</a></li> </ul> <h2>2.22.7 - 16 Nov 2023</h2> <ul> <li>Add a deprecation warning for customers using CodeQL version 2.11.5 and earlier. These versions of CodeQL were discontinued on 8 November 2023 alongside GitHub Enterprise Server 3.7, and will be unsupported by CodeQL Action v2.23.0 and later. <a href="https://redirect.github.com/github/codeql-action/pull/1993">#1993</a> <ul> <li>If you are using one of these versions, please update to CodeQL CLI version 2.11.6 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.</li> <li>Alternatively, if you want to continue using a version of the CodeQL CLI between 2.10.5 and 2.11.5, you can replace <code>github/codeql-action/*@v2</code> by <code>github/codeql-action/*@v2.22.7</code> in your code scanning workflow to ensure you continue using this version of the CodeQL Action.</li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/github/codeql-action/commit/b7bf0a3ed3ecfa44160715d7c442788f65f0f923"><code>b7bf0a3</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2099">#2099</a> from github/update-v3.23.2-61bf02577</li> <li><a href="https://github.com/github/codeql-action/commit/33e354b34bc9d95d28ae4f055fa1faeb59e59ae5"><code>33e354b</code></a> Changelog: Add missing PR link</li> <li><a href="https://github.com/github/codeql-action/commit/f4cfe8904c929c35f9612da0c754f121a3422d7e"><code>f4cfe89</code></a> Update changelog for v3.23.2</li> <li><a href="https://github.com/github/codeql-action/commit/61bf02577c801b30a708abc6f2164763e4e1d0cd"><code>61bf025</code></a> Send overall job status in init-post status report (<a href="https://redirect.github.com/github/codeql-action/issues/2097">#2097</a>)</li> <li><a href="https://github.com/github/codeql-action/commit/16150320c5db0d4942ea2bd4974fc365d6324737"><code>1615032</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2096">#2096</a> from github/update-bundle/codeql-bundle-v2.16.1</li> <li><a href="https://github.com/github/codeql-action/commit/bd67d8d6b2096e4b46db15ed108e563c4447d608"><code>bd67d8d</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2098">#2098</a> from github/henrymercer/update-internal-queries</li> <li><a href="https://github.com/github/codeql-action/commit/a2619f68c8432b9a500ecc7aafd4816667379bed"><code>a2619f6</code></a> Internal queries: Replace deprecated predicates</li> <li><a href="https://github.com/github/codeql-action/commit/666e2f9edfd29789e9f46f2cce092d18622dcb74"><code>666e2f9</code></a> Internal queries: Replace deprecated predicates</li> <li><a href="https://github.com/github/codeql-action/commit/d43ae36a631248dea35da2f8da5e28687255da31"><code>d43ae36</code></a> Add changelog note</li> <li><a href="https://github.com/github/codeql-action/commit/75af1f5948eef4f82d80db69296c55a9bc5ba26e"><code>75af1f5</code></a> Update default bundle to codeql-bundle-v2.16.1</li> <li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/012739e5082ff0c22ca6d6ab32e07c36df03c4a4...b7bf0a3ed3ecfa44160715d7c442788f65f0f923">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 #21168. PiperOrigin-RevId: 604910257 Change-Id: Ie6c8c18a6f4b8756b1f599894437e88a2d00f2ab
{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.
Follow our tutorials:
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.
See CONTRIBUTING.md
