commit e0e678f7d361e61b5bc510af25c5c682fe5a0682
author dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Wed Sep 11 00:51:02 2024 -0700
committer Copybara-Service <copybara-worker@google.com> Wed Sep 11 00:52:21 2024 -0700
tree 2521add4969d2016bbe49b7a98d1c94c417b038f
parent e8e1bd3c8e658ae3a40b7ce66f43ab446000de3e

Bump the github-actions group with 3 updates

Bumps the github-actions group with 3 updates: [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 `bazelbuild/continuous-integration` from 47d1cea8c6888d505a288065e067a03032d7aaac to 40accd1e24b7d296e87b573002ed0903828c0cf0
<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/40accd1e24b7d296e87b573002ed0903828c0cf0"><code>40accd1</code></a> Remove emergency banner (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2030">#2030</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/8b5d8e93b384fee9f84645b04ef53bf42cf5b88d"><code>8b5d8e9</code></a> Allow network-related env variables to be removed (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2029">#2029</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/3e3d3c147ce76e9323eb30f93d109b7d035ce757"><code>3e3d3c1</code></a> Disable rules_jsonnet  in downstream pipeline (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2027">#2027</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/e478ee5a6bf799dd707d7664ea58e18755237faa"><code>e478ee5</code></a> Retry on macos_arm64 on exit code 255 (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2026">#2026</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/26b4ba806422d9f298f1b3ad9b9e459361978414"><code>26b4ba8</code></a> Fix uploading artifact with buildkite-agent on Linux arm64 machine (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2024">#2024</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/e1b8edbe5ef7f37674534bdab0fbe9eac7b22964"><code>e1b8edb</code></a> Always set <code>publish_binary</code> to empty for generated rbe platforms (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2023">#2023</a>)</li>
<li><a href="https://github.com/bazelbuild/continuous-integration/commit/9588f08fbb6def72ba5eb9edf90d55228cf00b27"><code>9588f08</code></a> Publish linux arm64 binary for Bazel built at commits (<a href="https://redirect.github.com/bazelbuild/continuous-integration/issues/2022">#2022</a>)</li>
<li>See full diff in <a href="https://github.com/bazelbuild/continuous-integration/compare/47d1cea8c6888d505a288065e067a03032d7aaac...40accd1e24b7d296e87b573002ed0903828c0cf0">compare view</a></li>
</ul>
</details>
<br />

Updates `actions/upload-artifact` from 4.3.6 to 4.4.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.4.0</h2>
<h2>Notice: Breaking Changes :warning:</h2>
<p>We will no longer include hidden files and folders by default in the <code>upload-artifact</code> action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, <code>include-hidden-files</code>, to continue to do so.</p>
<p>See <a href="https://github.blog/changelog/2024-08-19-notice-of-upcoming-deprecations-and-breaking-changes-in-github-actions-runners/">&quot;Notice of upcoming deprecations and breaking changes in GitHub Actions runners&quot;</a> changelog and <a href="https://redirect.github.com/actions/upload-artifact/issues/602">this issue</a> for more details.</p>
<h2>What's Changed</h2>
<ul>
<li>Exclude hidden files by default by <a href="https://github.com/joshmgross"><code>@​joshmgross</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/598">actions/upload-artifact#598</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4.3.6...v4.4.0">https://github.com/actions/upload-artifact/compare/v4.3.6...v4.4.0</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/upload-artifact/commit/50769540e7f4bd5e21e526ee35c689e35e0d6874"><code>5076954</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/598">#598</a> from actions/joshmgross/exclude-hidden-files</li>
<li><a href="https://github.com/actions/upload-artifact/commit/d52396ac5d312b1bda1b9fe2ae55d862c65abd68"><code>d52396a</code></a> Add a warning about enabling <code>include-hidden-files</code></li>
<li><a href="https://github.com/actions/upload-artifact/commit/710f36207581d49e465ccbed3e007c317290fe11"><code>710f362</code></a> Remove &quot;merged&quot; from <code>include-hidden-files</code> input description</li>
<li><a href="https://github.com/actions/upload-artifact/commit/3b315f26f6f828f74089e1863e67e60e48e37563"><code>3b315f2</code></a> <code>npm run release</code> again 🙂</li>
<li><a href="https://github.com/actions/upload-artifact/commit/3be2180eb79b56341b1b127ca06a5adba2a5a3e4"><code>3be2180</code></a> Remove another trailing comma</li>
<li><a href="https://github.com/actions/upload-artifact/commit/453e8d0a40444939146df5febed0b1221b9dd073"><code>453e8d0</code></a> Update glob license</li>
<li><a href="https://github.com/actions/upload-artifact/commit/0a398c14804ead69f18a166f0a99f91239261ee5"><code>0a398c1</code></a> <code>npm run release</code></li>
<li><a href="https://github.com/actions/upload-artifact/commit/a0c40cf60283f329afac2bc0fa77f1a59fa11e6e"><code>a0c40cf</code></a> Update to latest <code>@actions/glob</code> and fix tests</li>
<li><a href="https://github.com/actions/upload-artifact/commit/acb59e47763b6e601a344d04cf3c082ee336b709"><code>acb59e4</code></a> <code>lint</code></li>
<li><a href="https://github.com/actions/upload-artifact/commit/cb6558bb10fe4afe4054d0be4b3136e673eb5e7f"><code>cb6558b</code></a> Exclude hidden files by default</li>
<li>See full diff in <a href="https://github.com/actions/upload-artifact/compare/834a144ee995460fba8ed112a2fc961b36a5ec5a...50769540e7f4bd5e21e526ee35c689e35e0d6874">compare view</a></li>
</ul>
</details>
<br />

Updates `github/codeql-action` from 3.26.1 to 3.26.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.26.6 - 29 Aug 2024</h2>
<ul>
<li>Update default CodeQL bundle version to 2.18.3. <a href="https://redirect.github.com/github/codeql-action/pull/2449">#2449</a></li>
</ul>
<h2>3.26.5 - 23 Aug 2024</h2>
<ul>
<li>Fix an issue where the <code>csrutil</code> system call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled. <a href="https://redirect.github.com/github/codeql-action/pull/2441">#2441</a></li>
</ul>
<h2>3.26.4 - 21 Aug 2024</h2>
<ul>
<li><em>Deprecation:</em> The <code>add-snippets</code> input on the <code>analyze</code> Action is deprecated and will be removed in the first release in August 2025. <a href="https://redirect.github.com/github/codeql-action/pull/2436">#2436</a></li>
<li>Fix an issue where the disk usage system call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled, and then surface a warning. The system call is now disabled for these machines. <a href="https://redirect.github.com/github/codeql-action/pull/2434">#2434</a></li>
</ul>
<h2>3.26.3 - 19 Aug 2024</h2>
<ul>
<li>Fix an issue where the CodeQL Action could not write diagnostic messages on Windows. This issue did not impact analysis quality. <a href="https://redirect.github.com/github/codeql-action/pull/2430">#2430</a></li>
</ul>
<h2>3.26.2 - 14 Aug 2024</h2>
<ul>
<li>Update default CodeQL bundle version to 2.18.2. <a href="https://redirect.github.com/github/codeql-action/pull/2417">#2417</a></li>
</ul>
<h2>3.26.1 - 13 Aug 2024</h2>
<p>No user facing changes.</p>
<h2>3.26.0 - 06 Aug 2024</h2>
<ul>
<li><em>Deprecation:</em> Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you. <a href="https://redirect.github.com/github/codeql-action/pull/2403">#2403</a></li>
<li>Bump the minimum CodeQL bundle version to 2.13.5. <a href="https://redirect.github.com/github/codeql-action/pull/2408">#2408</a></li>
</ul>
<h2>3.25.15 - 26 Jul 2024</h2>
<ul>
<li>Update default CodeQL bundle version to 2.18.1. <a href="https://redirect.github.com/github/codeql-action/pull/2385">#2385</a></li>
</ul>
<h2>3.25.14 - 25 Jul 2024</h2>
<ul>
<li>Experimental: add a new <code>start-proxy</code> action which starts the same HTTP proxy as used by <a href="https://github.com/github/dependabot-action"><code>github/dependabot-action</code></a>. Do not use this in production as it is part of an internal experiment and subject to change at any time. <a href="https://redirect.github.com/github/codeql-action/pull/2376">#2376</a></li>
</ul>
<h2>3.25.13 - 19 Jul 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/4dd16135b69a43b6c8efb853346f8437d92d3c93"><code>4dd1613</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2452">#2452</a> from github/update-v3.26.6-7233ec5e6</li>
<li><a href="https://github.com/github/codeql-action/commit/dd9dd2d5389e8ca48a8201513c3fd18d7fda567d"><code>dd9dd2d</code></a> Update changelog for v3.26.6</li>
<li><a href="https://github.com/github/codeql-action/commit/7233ec5e6b313c47141f047dd5be5f957560dd27"><code>7233ec5</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2449">#2449</a> from github/update-bundle/codeql-bundle-v2.18.3</li>
<li><a href="https://github.com/github/codeql-action/commit/a32c44dba17a9c6628320a29508e84e052128a3a"><code>a32c44d</code></a> Add changelog note</li>
<li><a href="https://github.com/github/codeql-action/commit/2966897c6759237a41ccd8fd392565a4e86a5121"><code>2966897</code></a> Update default bundle to codeql-bundle-v2.18.3</li>
<li><a href="https://github.com/github/codeql-action/commit/b8efe4dc6ab6d31abe3ec159420d2a4916880800"><code>b8efe4d</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2435">#2435</a> from github/update-supported-enterprise-server-versions</li>
<li><a href="https://github.com/github/codeql-action/commit/ab408a875b0616b0e5eaa4d0d86ac836a29cfb4e"><code>ab408a8</code></a> Merge branch 'main' into update-supported-enterprise-server-versions</li>
<li><a href="https://github.com/github/codeql-action/commit/864b979bc3eb6b10501334cb368b2b398a60ff1b"><code>864b979</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2443">#2443</a> from github/dbartol/config-file-telemetry</li>
<li><a href="https://github.com/github/codeql-action/commit/d36c7aaf6a9744943ec1ee06e31a6dd1eb8e1357"><code>d36c7aa</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/2448">#2448</a> from github/dependabot/npm_and_yarn/npm-09b7c43f6b</li>
<li><a href="https://github.com/github/codeql-action/commit/b3bf514df4c04374e8f0db7938b20f8425387f33"><code>b3bf514</code></a> Update checked-in dependencies</li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/29d86d22a34ea372b1bbf3b2dced2e25ca6b3384...4dd16135b69a43b6c8efb853346f8437d92d3c93">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 #23485.

PiperOrigin-RevId: 673274405
Change-Id: I691d81a6d63f2d4a431473272c9917dddd4bb120