obsidian-remote-ssh

Changelog & releases

3 min read

Changelog & releases

Per-release notes are auto-generated by git-cliff (Conventional Commits → grouped Markdown) and live on the GitHub Releases page — that’s the canonical source. This page is a navigational entry point + the major-milestone overview.

Where to find what

You want…Look at
Full per-release commit logGitHub Releases (each entry has a Markdown changelog body)
Just the latest stableLatest release
Just the latest beta (BRAT)Pre-releases filter
A specific version’s binaries + signatureshttps://github.com/sotashimozono/obsidian-remote-ssh/releases/tag/<X.Y.Z>
What’s coming nextRoadmap

Major milestones

1.0.44 — comprehensive docs + two-channel system mature

Stable promotion that brought the formalised next/main two-channel release model + 49 pages of end-user docs site (this very docs site you’re reading) to stable distribution. After this point the development cadence settles: every BRAT user runs the same plugin codebase as the Community Plugins store version, with the latter trailing the former by one promotion cycle.

1.0.43 — two-channel system born

The pre-1.0.43 promotion was painful enough to motivate a redesign:

  • next (integration) + main (stable) explicit channels
  • bump-version.mjs becomes branch-aware (beta-only vs stable-everything file updates)
  • version-check.yml becomes branch-aware (semver-aware compare, channel-pinned manifest invariants)
  • release.yml reads version shape to select prerelease vs stable
  • sync-main-to-next.yml automates the post-promotion back-sync
  • All five workflows extended to cover both next and main

Before 1.0.43, channel separation was implicit (every version was effectively beta; promotions were ad-hoc).

1.0.0 — first stable cut

The shadow-vault architecture became the canonical one. Pre-1.0 prototypes (reconcileVaultRoot + monkey-patch approach, see Shadow vault architecture) were retired. manifest-beta.json introduced; BRAT distribution went live. From 1.0.0, the plugin was considered fit-for-purpose for early adopters.

Submitted to the Obsidian Community Plugins store at this point — see obsidianmd/obsidian-releases#12390.

0.4.x series — feature build-out

The vast majority of feature work (auth, reconnect, jump hosts, host-key trust, fs.thumbnail, terminal pane, Phase A multi-client tests, Phase D logger + cosign signing) landed across the 0.4.x line. See the GitHub Releases page filtered to 0.4 for the full chronological list.

0.3.0 — first published release

Initial public artefacts. The plugin existed before this as in-development scaffolding; 0.3.0 was the first version with a tagged release on GitHub.

Reading a release entry

Each release body is structured by Conventional Commits type:

## ✨ Features
- description (commit-sha)

## 🐛 Bug Fixes
- ...

## 🚧 CI
- ...

## 🧹 Chores

Configured in cliff.toml (repo root). Dependabot-noise commits are suppressed; merge commits are excluded; Co-Authored-By: trailers are stripped from the rendered output. The (commit-sha) link goes to the commit on GitHub.

How a version number maps to a release

PatternChannelExample
X.Y.Z (no suffix)Stable — appears on Community Plugins store1.0.44
X.Y.Z-beta.NBeta — BRAT --beta consumers see these1.0.45-beta.3

The version shape is the single source of truth for which channel a release belongs to. See Release & deploy pipeline for the machinery that enforces this.

Subscribing to releases

Two ways to be notified of new releases:

  1. GitHub watch — repo page → Watch → Custom → tick “Releases”.
  2. Atom feed — https://github.com/sotashimozono/obsidian-remote-ssh/releases.atom (point any feed reader at it).

For BRAT users, no subscription is needed — BRAT auto-fetches the latest prerelease on every Obsidian launch.

See also

Graph View

Backlinks