chore(deps): bump softprops/action-gh-release from 2 to 3 - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/softprops/action-gh-release-3
branch
from
July 17, 2026 18:12
5e44bb0 to
1ee6743
Compare
Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 2 to 3. - [Release notes](https://github.com/softprops/action-gh-release/releases) - [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md) - [Commits](softprops/action-gh-release@v2...v3) --- updated-dependencies: - dependency-name: softprops/action-gh-release dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/softprops/action-gh-release-3
branch
from
July 17, 2026 18:13
1ee6743 to
b41e036
Compare
Owner
|
Superseded by #15 (batched GitHub Actions bumps). |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/softprops/action-gh-release-3
branch
July 17, 2026 18:40
DevVig
added a commit
that referenced
this pull request
Jul 18, 2026
## What Adds a **Tauri in-app self-updater** alongside the existing Homebrew path — and makes it **channel-aware** so the two can't drift. ### The drift problem this avoids A brew-installed `.app` that silently self-updates diverges from the formula version, and the next `brew upgrade` fights it. So the updater checks how the app was installed: - **Homebrew installs** (formula drops a `.microbridge-brew` marker at the bundle root) → "Check for Updates…" points the user at `brew upgrade microbridge`. Never self-replaced. - **Direct / DMG installs** → full Tauri flow: `check()` → confirm → `downloadAndInstall()` → `relaunch()`. ### Staying honest with principle #2 ("Zero network, no update pings") - The **daemon stays 100% network-free** — the updater lives entirely in the UI app. - **User-initiated by default.** No background polling, no timers. - An **opt-in** "check once at launch" toggle exists (off by default); when on, it checks silently and only speaks up if an update is ready. ## Changes - `tauri-plugin-updater` / `-process` / `-dialog` wired into the menu bar app (Rust + JS + capabilities). - `update_channel` + `app_version` commands (`src-tauri/src/lib.rs`). - **"Check for Updates…"** tray menu item → emits `menu://check-updates`; the always-loaded popover runs the flow. - New **Updates** settings tab: version, install channel, opt-in launch-check toggle, manual check button. - `plugins.updater` config with the committed public key + the stable GitHub `releases/latest/download/latest.json` endpoint. ## Not in this PR (follow-up) Release plumbing — `bundle.createUpdaterArtifacts`, signing the updater tarball in CI, and generating/uploading `latest.json`. Until that ships with `v0.2.0`, `check()` simply finds no manifest and no-ops gracefully. The updater signing keypair + GitHub secrets are already in place. ## Verification - `npm run build` (tsc + vite) ✅ - `cargo build` on the tauri crate ✅ — compiles, and tauri's build script validates the new `plugins.updater` config and capability permissions. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
DevVig
added a commit
that referenced
this pull request
Jul 18, 2026
## What Completes the in-app self-updater (follow-up to #41) by producing the artifacts it consumes at release time. ### Release plumbing - **`bundle.createUpdaterArtifacts: true`** → `tauri build` emits the signed `Microbridge.app.tar.gz` + `.sig` updater bundle alongside the `.app`/DMG. - **Signing secrets** (`TAURI_SIGNING_PRIVATE_KEY` + `_PASSWORD`) exported into the UI build. Already set on the repo. Forks without the key still build — updater artifacts auto-disable via a `--config` override, so releases never hard-fail. - **Per-arch packing**: the updater tarball is renamed `Microbridge-<target>.app.tar.gz` so the two matrix legs don't collide as release assets. - **`latest.json`** generated in the publish job (via `jq`, from the `.sig` contents) with `darwin-aarch64` + `darwin-x86_64` entries, and uploaded as a release asset. The app's endpoint `releases/latest/download/latest.json` always resolves to the newest release. ### Docs - README principle #2 reworded: the **daemon stays zero-network**; the app's *only* network call is the **opt-in, user-triggered** update check. No background pings. - INSTALL.md documents the in-app update path for direct installs and the brew-managed behavior. ## Channel safety (recap from #41) Brew installs carry a `.microbridge-brew` marker; the app routes those to `brew upgrade` and never self-replaces, so the formula version and the on-disk bundle can't drift. Direct/DMG installs self-update. ## How it's exercised This runs on the next `v*` tag (targeting `v0.2.0`). Merge order matters only in that both this and #41 must be on `main` before tagging — no release is cut before then. ## Verification - `release.yml` validated as YAML; `tauri.conf.json` valid JSON with `createUpdaterArtifacts: true`. - `cargo build` on the tauri crate passes with the config change. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps softprops/action-gh-release from 2 to 3.
Release notes
Sourced from softprops/action-gh-release's releases.
... (truncated)
Changelog
Sourced from softprops/action-gh-release's changelog.
Commits
3d0d988release 3.0.2 (#818)7e13ed4fix: clarify release creation 404 errors (#817)e6c70a5fix: replace existing release assets on Gitea (#816)f345337fix: publish existing draft releases as prereleases (#801)d8a89a2fix: upload small checksum assets reliably (#815)45ece40chore(deps): remove unused TypeScript tooling (#814)f6b913cfeat: improve release error reporting and test coverage (#813)15f193dchore(deps): upgrade TypeScript to 7 (#812)cc8268dchore(deps): bump actions/checkout in the github-actions group (#810)fd0ed1echore(deps): bump the npm group with 3 updates (#811)