Skip to content

chore(release): prepare SlashIt v0.0.4 prerelease - #365

Merged
shingonoide merged 5 commits into
mainfrom
release/0.0.4-preparation
Nov 18, 2026
Merged

shingonoide merged 5 commits into
mainfrom
release/0.0.4-preparation

Conversation

@shingonoide

Copy link
Copy Markdown
Contributor

Summary

Prepares the SlashIt 0.0.4 experimental prerelease: version declarations, the release channel, the CHANGELOG section, and the installation guide.

This PR does not create the v0.0.4 tag, run the release workflow, sign anything, publish an installer, or change the AppImage packaging or the WebKitGTK mitigation.

What is prepared

  • Version 0.0.4 in the Cargo workspace and crate manifests, Cargo.lock (nine workspace packages), src-tauri/tauri.conf.json, package.json, and package-lock.json. The version bump was produced by scripts/release-bump.sh. The change is version fields only; no dependency changes.
  • .github/release-channels.txt declares 0.0.4 prerelease.
  • CHANGELOG.md: the [0.0.4] section, the [Unreleased] link, and the [0.0.4] comparison link.
  • docs/installation.md: separates the recorded 0.0.3 results from the 0.0.4 changes and states that no 0.0.4 installer, launch, or update has been tested. It also covers required backups and the downgrade limitation.
  • Corrections in this PR:
    • The Human Review entry now names the two refused paths: pull-request creation without a current approval, and slashit move <task> done.
    • The installation guide attributes its .deb dependency and maintainer-script facts to the 0.0.2 package that was inspected, not to 0.0.3 or 0.0.4.

What has been validated

What remains untested

  • Rust formatting, clippy, and the Rust test suite were not run locally. Hosted CI runs them on this PR.
  • No 0.0.4 artifact (AppImage, .deb, .rpm, .msi, NSIS .exe, .dmg) has been built, installed, or launched.
  • The contents of the 0.0.4 packages (payload, bundled WebKitGTK version) have not been inspected.
  • The in-app updater has not been run for 0.0.4.
  • Packaged Git over HTTPS (issue AppImage: Git over HTTPS fails because bundled libraries shadow host libraries #280) has not been confirmed in a packaged build.
  • Downgrade to a 0.0.3 binary has not been tested, and restoring a backup has not been tested.

Known limitations

  • This is an experimental prerelease and is not production-ready.
  • Issue Linux AppImage: intermittent SIGKILL of main process during startup #269 (AppImage startup SIGKILL) remains open. The 0.0.3 mitigation is kept, and the upstream WebKitGTK behavior is not fixed.
  • A board written by 0.0.4 can be unreadable by 0.0.3 when a Task uses a field 0.0.4 added. Back up SlashIt data before installing and before any downgrade.
  • The installers are not code-signed.

Steps after merge

  1. Confirm the merge commit's tree matches this PR's head tree.
  2. Obtain the owner's separate authorization before pushing the v0.0.4 tag, which starts the release workflow and creates a draft release.
  3. Validate the workflow's actual artifacts following docs/releasing.md, section 5, before publishing the draft.
  4. Update the installation guide's verification table only from recorded results for the built artifacts.

@coderabbitai

coderabbitai Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Explain Change →

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: BarraDev/slashit
  • Branch: main
  • File: .coderabbit.yaml
  • Commit: 6c2da69
  • Layers: Repository YAML (base), Repository UI (inherited)
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: c88aa873-de7e-4f34-af16-bae830feedd1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
Walkthrough

The release metadata and package version fields change to 0.0.4, which is marked as a prerelease. The changelog records the release contents and known issues. The installation guide lists expected artifacts, identifies verification that has not been completed, and updates platform, downgrade, updater, and backup guidance.

Possibly related PRs

  • BarraDev/slashit#262: Establishes the release preflight and prerelease-channel configuration used by this release.
  • BarraDev/slashit#266: Defines release-channel classification that uses the channel and version fields updated here.
  • BarraDev/slashit#276: Adds the previous release’s installation documentation, which this guide updates with 0.0.4 information.

Change: Other

Merge Risk: Low · previous review ebe37

The 0.0.4 prerelease preparation is consistent. The restore instructions should tell users to stop slashitd as well as SlashIt before restoring a backup, as the backup step already does. A restore that runs while the daemon is writing could leave the board or worktrees inconsistent.

Pre-merge checks: Passed 5

Check name Status Explanation
Title check Passed The title names the change: a release-preparation chore that bumps SlashIt to v0.0.4 as a prerelease. The changeset matches this, with version fields across manifests, the release-channel entry, the C…
Description check Passed The description is detailed and matches the changeset. It covers the version bumps in Cargo, Tauri, and npm manifests, the release-channel declaration, the CHANGELOG section, and the installation guid…
Persistent State Integrity Passed The check is PASS because this PR changes no code that mutates persisted application state. Evidence from the reviewed range (refs/coderabbit/pre-merge-check/base..head): - The changed-file list has 1…
Recoverable Resource Lifecycle Passed The check covers changes to worktree, task, migration, or cleanup lifecycle code. This PR does not change any such code. The changed-file inventory has 16 files: .github/release-channels.txt, `CHANG…
Platform Boundary Safety Passed The check is applicable only if the PR changes code that uses platform-specific APIs or affects the cross-platform build. The PR diff (base to head) touches 16 files, and none of them is Rust source. …
Full details: Title check

Explanation

The title names the change: a release-preparation chore that bumps SlashIt to v0.0.4 as a prerelease. The changeset matches this, with version fields across manifests, the release-channel entry, the CHANGELOG section, and the installation guide. The title is specific and accurate, and it does not claim work outside the PR. It is a chore prefix, not a user-visible feature, which fits the requirement to describe the primary change without overclaiming.

Full details: Description check

Explanation

The description is detailed and matches the changeset. It covers the version bumps in Cargo, Tauri, and npm manifests, the release-channel declaration, the CHANGELOG section, and the installation guide. It also lists validation, untested areas, and known limitations. It is clearly related to the changes and is not off-topic.

Full details: Persistent State Integrity

Explanation

The check is PASS because this PR changes no code that mutates persisted application state. Evidence from the reviewed range (refs/coderabbit/pre-merge-check/base..head): - The changed-file list has 17 files. They are version manifests (Cargo.toml files, Cargo.lock, package.json, package-lock.json, src-tauri/tauri.conf.json), .github/release-channels.txt, CHANGELOG.md, and docs/installation.md. - A search of *.rs, *.ts, *.tsx, *.js, and *.sh files returned no hunks. No source code changed. - The lockfile and manifest hunks are version-field edits only (0.0.3 to 0.0.4). No dependency or logic changes appear in the diff. Neither the changelog nor the installation guide writes to persistent state. Because no changed code path mutates persistence, the failure conditions (false success after a failed write, publishing unpersisted state, or a stale read-modify-write) cannot be triggered by this PR.

Full details: Recoverable Resource Lifecycle

Explanation

The check covers changes to worktree, task, migration, or cleanup lifecycle code. This PR does not change any such code. The changed-file inventory has 16 files: .github/release-channels.txt, CHANGELOG.md, docs/installation.md, Cargo.lock, package-lock.json, package.json, src-tauri/tauri.conf.json, and the Cargo manifests (workspace, crates, and src-tauri). Patch review of the manifests, package.json, tauri.conf.json, and the lockfiles shows only version field changes from 0.0.3 to 0.0.4, plus the release-channel line 0.0.4 prerelease. The CHANGELOG and installation guide are documentation. They describe the Task-field downgrade behavior and the backup guidance, but they change no runtime code. No worktree, task, migration, or cleanup logic is modified, so no lifecycle change can clear or destroy a persisted resource reference. The check is inapplicable.

Full details: Platform Boundary Safety

Explanation

The check is applicable only if the PR changes code that uses platform-specific APIs or affects the cross-platform build. The PR diff (base to head) touches 16 files, and none of them is Rust source. The Rust-related changes are limited to version fields in Cargo.toml manifests and the nine workspace package entries in Cargo.lock. The Tauri config and package.json contain version-only changes. The remaining changes are .github/release-channels.txt (adds 0.0.4 prerelease), CHANGELOG.md, and docs/installation.md. No cfg(unix)/cfg(windows) gating, platform API, build script, or dependency change was introduced. The PR cannot introduce a platform boundary or cross-platform compile failure through these edits. The check passes.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review info

Run configuration

  • Source mode: Auto
  • Repository: BarraDev/slashit
  • Branch: main
  • File: .coderabbit.yaml
  • Commit: 6c2da69
  • Layers: Repository YAML (base), Repository UI (inherited)
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: a8c2277e-bf0f-433c-b669-856cd85e4082
Commits

Reviewing files that changed from the base of the PR and between 6c2da69 and ebe3761.

Files ignored due to path filters: 2

  • Cargo.lock is excluded by !**/*.lock
  • package-lock.json is excluded by !**/package-lock.json
Files selected for processing: 14

  • .github/release-channels.txt
  • CHANGELOG.md
  • Cargo.toml
  • crates/slashit-acceptance/Cargo.toml
  • crates/slashit-activity/Cargo.toml
  • crates/slashit-attention/Cargo.toml
  • crates/slashit-cli/Cargo.toml
  • crates/slashit-durable-fs/Cargo.toml
  • crates/slashit-ipc/Cargo.toml
  • crates/slashit-review-content/Cargo.toml
  • docs/installation.md
  • package.json
  • src-tauri/Cargo.toml
  • src-tauri/tauri.conf.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Comment thread docs/installation.md Resolved
shingonoide added a commit that referenced this pull request Nov 18, 2026
…366)

## Summary

- Sidebar: show the canonical `logo.svg` in place of the generic
gradient `S`, and drop the "Task orchestration" subtitle. The collapsed
sidebar shows the logo alone with the accessible name `SlashIt`.
- Linux tray: the hover name is the StatusNotifierItem `Title`.
libayatana takes it from the GLib application name, which defaulted to
the binary name (`slashit-ui`). The application name is now set to
`SlashIt` before the tray is built.

## Changes

- `index.html`: one Trunk `copy-file` directive for `logo.svg`, so the
build serves the same file as the repository root.
- `src/components/sidebar.rs`: the header renders the logo image in both
states.
- `src-tauri/src/lib.rs`: a Linux-only call to
`g_set_application_name("SlashIt")` in the tray setup, declared with
`extern "C"` like the existing declarations in `rtprio_guard.rs`. No
dependency is added.

## Root cause (tray)

`tauri::tray::TrayIconBuilder::tooltip` is ignored by the
libappindicator backend, which the default `tray-icon` features select
on Linux. `.title()` maps to a persistent label, not a hover name. The
live item's `Title` property was `slashit-ui`, and `ToolTip` was empty.
A scratch probe that uses the same libappindicator calls showed `Title`
= the program name by default and `SlashIt` after
`g_set_application_name("SlashIt")`.

## Not changed

- Binary name, `productName`, bundle identifier
`com.barradev.slashit-app`, IPC, persistent paths, updater.
- Program name (`g_get_prgname`) and therefore the process name.
- CHANGELOG: deferred until PR #365 lands, to avoid a conflict.

## Validation

- `cargo check -p slashit-ui`: passes, no warnings.
- `cargo clippy -p slashit-ui -p slashit -- -D warnings`: passes.
- `cargo test -p slashit-frontend`: 401 and 3 passed.
- `trunk build`: succeeds, and `logo.svg` in the output is
byte-identical to the root asset.
- Browser check of the built frontend, with a scratch stub for
`window.__TAURI__`: expanded sidebar shows the logo and `SlashIt`, the
tagline is absent, no `S` glyph remains, the logo loads, collapse and
expand work, and navigation works. Console showed only the errors from
the stubbed backend.
- Tray: verified with a standalone libappindicator probe on the owner's
session (`Title` changes from the program name to `SlashIt`). The full
application was not run for this PR.

## Limits

- The sidebar was not checked inside the Tauri webview. The acceptance
harness cannot run on this machine (no `WebKitWebDriver`).
- The tray fix is verified on the libayatana backend only. On a host
that uses a different StatusNotifierItem client, the displayed name
should still follow `Title`, but it was not tested there.
@shingonoide
shingonoide merged commit 3d23039 into main Nov 18, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant