Bumps [mlugg/setup-zig](https://github.com/mlugg/setup-zig) from 1 to 2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/mlugg/setup-zig/releases">mlugg/setup-zig's
releases</a>.</em></p>
<blockquote>
<h2>v2.0.0</h2>
<ul>
<li>Support getting Zig version from <code>build.zig.zon</code></li>
<li>Add option to customize cache key to work around matrix
deficiencies</li>
<li>Clear Zig cache directory when it grows too large</li>
</ul>
<h2>v1.2.2</h2>
<blockquote>
<p>[!WARNING]
Assuming no serious bugs, this will be the last v1 release. <strong>I
highly recommend upgrading to v2.</strong></p>
</blockquote>
<ul>
<li>Update mirror list</li>
<li>Update dependencies
<ul>
<li>This includes the cache service, resolving <a
href="https://redirect.github.com/mlugg/setup-zig/issues/36">#36</a>;
sorry about that one!</li>
</ul>
</li>
<li>Validate minisign "trusted comment"</li>
</ul>
<h2>v1.2.1</h2>
<ul>
<li>Fix <code>.zip</code> tarball extraction</li>
<li>Add two new mirrors</li>
<li>Don't attempt to cache global Zig cache if it doesn't exist (<a
href="https://redirect.github.com/mlugg/setup-zig/issues/8">#8</a>)</li>
</ul>
<h2>v1.2.0</h2>
<ul>
<li>Add the <code>use-cache</code> option to disable preservation of the
Zig global cache directory</li>
</ul>
<h2>v1.1.1</h2>
<ul>
<li>Fix the restriction of <code>mirror</code> to not be
<code>ziglang.org</code> (I forgot to implement it before)</li>
<li>Append query parameter to downloads so mirrors can know that traffic
is coming from Actions</li>
<li>Add new mirror (thanks <a
href="https://github.com/hryx"><code>@hryx</code></a>!)</li>
</ul>
<h2>v1.1.0</h2>
<ul>
<li>Support looking up Mach nominated versions, e.g.
<code>2024.5.0-mach</code></li>
<li>Support overriding download mirror</li>
</ul>
<p>See README.md for details.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="aa9ad5c14e"><code>aa9ad5c</code></a>
README: reference setup-zig@v2</li>
<li><a
href="851448343a"><code>8514483</code></a>
chore: Temporarily remove mirror (maintenance)</li>
<li><a
href="915f70607f"><code>915f706</code></a>
post: harden totalSize against fs races</li>
<li><a
href="9d38a7af8e"><code>9d38a7a</code></a>
minisign: fix typo</li>
<li><a
href="c912213482"><code>c912213</code></a>
Update machengine mirror ownership info</li>
<li><a
href="e1d6dd251f"><code>e1d6dd2</code></a>
Support Mach nominated versions in <code>build.zig.zon</code></li>
<li><a
href="9ac9efd667"><code>9ac9efd</code></a>
Clear Zig cache directory when it grows too large</li>
<li><a
href="0a889b2ab1"><code>0a889b2</code></a>
Update <code>@actions/cache</code> to 4.0.2</li>
<li><a
href="0f2d1f2660"><code>0f2d1f2</code></a>
Validate trusted comment in minisign signature</li>
<li><a
href="806c1bbc96"><code>806c1bb</code></a>
Add option to customize cache key</li>
<li>Additional commits viewable in <a
href="https://github.com/mlugg/setup-zig/compare/v1...v2">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
You can trigger a rebase of this PR 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 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)
</details>
> **Note**
> Automatic rebases have been disabled on this pull request as it has
been open for over 30 days.
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The GitHub ARM runners have some bad dependencies. I'm adding a `snap
refresh` and `lxd init` to ensure these dependencies are good before we
run the build.
I'm also updating to the latest `electron-builder` and
`electron-updater`.
edited didn't do what i thought it did, it actually gets triggered if
the comments or title change, which we don't want. synchronize is for
when the head changes
I'm making steps to simplify our build dependencies, consolidating our C
compiler requirements so we only depend on Zig.
Before, we used Zig for x64 but not for arm64. This meant that users
using an ARM dev machine would need to install `build-essentials` and
Zig. We also required MinGW-w64 on Windows, which is a pain to install
since it can be provided by a bunch of different tools, the smallest of
which is like a 2GB install.
Also moves icon and color definitions to the backend and makes it so the
new workspaces get created with a different icon color for each index.
If an ephemeral window has more than one tab, always create a new window
when switching workspaces
Also fixes workspace accelerators on macOS
Because Electron now has a macOS 11 minimum supported version, we have
no blockers to adopting the latest Go toolchain. This also lets us use
the new `range` features in Go, among other things.
This adds the new tasks `docsite:start`, `docsite:build:public`,
`docsite:build:embedded`, `storybook:build`, and `copyfiles:*:*` to
Taskfile.
It also updates the "Build Helper" and "Docsite and Storybook CI/CD"
workflows to use these new tasks.
It also makes the docsite embedded build a dependency of the electron
tasks, ensuring that the embedded docsite is included when building
locally.
Tested and confirms this works on Windows
NodeJS 20 is almost EOL so I'm updating our workflows to use NodeJS 22.
This does not change anything about our app, which will still use NodeJS
20 until Electron shifts away from it. NodeJS 22 is fully
backwards-compatible with NodeJS 20 so there's no issue from a testing
standpoint.
## Summary
We are moving our docsite to this repo for better coordination.
## What's changed?
- The docsite codebase is now in docs/
- The docsite will replace storybook as the published GitHub Pages site
for this repo
- Storybook will now be hosted at https://docs.waveterm.dev/storybook
- A new CI workflow will validate any changes to Storybook or the
docsite
- A combined CD workflow will build and deploy Storybook and the docsite
as a single artifact
- The Build Helper workflow will now build an embedded version of the
docsite before building the app, ensuring the docsite version it has is
always the latest
There was a race condition in the Build Helper where if multiple runners
got to the "Create draft release" step at the same time, we could get
duplicate releases created. Now, each of the build runners will upload
the artifacts to the workflow artifact feed. Then, a single runner will
create the draft release.
