1.0.7

A description fix. No code changes, nothing behaves differently, and there is nothing to do on upgrade.

Requires Obsidian 1.7.2 or later, unchanged.

Changed

The description opened with the plugin's own name, which the directory asks you not to do. The listing prints the name directly above the description, so repeating it spends the first and most valuable words saying nothing.

Before

Stashwise reads the videos, posts and articles you save from your phone and writes the summary and key points. Those notes land in your vault, ready to search, link and build on.

After

Save a video, post or article from your phone and Stashwise reads it for you. The summary, takeaways and topics arrive in your vault as notes you can search and link.

scripts/verify-manifest.mjs now checks this, along with the listing's character cap, and runs as part of the lint step so a release cannot repeat it.

Note on this release

GitHub Actions was in a major outage when this was tagged, and the release workflow was cancelled in the queue without running. The assets here were built from tag 1.0.7 with the same commands the workflow uses, and the tests, lint and mobile safety gate all passed. They do not carry build provenance attestations, because those can only be produced inside the workflow. Earlier releases have them, and later ones will again.

Full changelog: 1.0.6...1.0.7

1.0.6

A description rewrite. No code changes, nothing behaves differently, and there is nothing to do on upgrade.

Requires Obsidian 1.7.2 or later, unchanged.

Changed

The old description assumed you already knew what a Stashwise library and wiki were, and led with the mechanism. Someone seeing the name for the first time had no reason to care.

Before

Sync your Stashwise library and wiki into your vault, search it from any note, and capture notes back.

After

Stashwise reads the videos, posts and articles you save from your phone and writes the summary and key points. Those notes land in your vault, ready to search, link and build on.

It now says what Stashwise does for you and where the material comes from, which is your phone. The mechanism is still there, at the end, where it belongs.

Full changelog: 1.0.5...1.0.6

1.0.5

Fixes the description the directory rejected, and closes the gap that let it through.

Requires Obsidian 1.7.2 or later, unchanged. Nothing to do on upgrade, and nothing behaves differently.

Changed

• The plugin description no longer contains the word "Obsidian", which the directory does not allow because the context already implies it. It still says the part worth knowing: share a video or article from your phone and the processed note is waiting in your vault.
• manifest.json is now covered by the lint run. It never was: the rule that validates it returns early unless the manifest is the file being linted, while the recommended configuration only applies it to source files. So a clean lint reported nothing about the manifest at all.

That gap immediately surfaced a second constraint the first was masking. Descriptions are limited to letters, digits, whitespace and a short list of punctuation that excludes the colon, so the previous wording would have been rejected again on the following round.

Full changelog: 1.0.4...1.0.5

1.0.4

Settings are now findable in Obsidian's settings search, and the plugin's description finally says you can capture from your phone.

Requires Obsidian 1.7.2 or later, unchanged. Nothing to do on upgrade.

Changed

• The settings tab adopts Obsidian's declarative settings API, so on 1.13.0 and later its settings appear in the settings search. Below 1.13 nothing changes.
• The plugin description now mentions the part that is hardest to guess: share a video, post or article to Stashwise from any app on your phone, and the processed note is waiting in your vault the next time Obsidian opens on that phone.

How the settings tab is built, for anyone reading the source

Obsidian renders a settings tab one way or the other and never both. On 1.13 and later it uses the declarative definitions; below that it uses the older imperative path. Keeping a separate list for each would fail quietly, since a row missing from one list disappears only for the versions using that renderer.

So neither renderer holds any content. One description of the rows feeds both, which means a row cannot exist on one version and not the other.

Full changelog: 1.0.3...1.0.4

1.0.3

Clears four of the five advisories the directory raised against 1.0.2. No errors were outstanding; this is housekeeping.

Requires Obsidian 1.7.2 or later, unchanged. Nothing to do on upgrade, and nothing visibly different.

Changed

• Internal redraws of the settings tab no longer call the deprecated display(). Obsidian still calls it to open the tab; our own refreshes after connect, disconnect and token paste go through a private method instead.
• The Disconnect button applies the mod-warning class directly rather than calling setWarning(), which is deprecated in favour of an API that requires Obsidian 1.13.0. It renders identically on every supported version.

Known and deliberate

The settings tab does not implement getSettingDefinitions(), so its settings do not appear in Obsidian's settings search on 1.13.0 and later. Adopting that API is all or nothing: Obsidian renders either the declarative definitions or display(), never both, so a partial conversion would drop settings for anyone on the newer version. It is a full rewrite that needs testing either side of 1.13, and it is tracked rather than rushed.

minAppVersion stays at 1.7.2 so the plugin keeps working on phones that have not updated, which is where its capture flow matters most.

Full changelog: 1.0.2...1.0.3

1.0.2

Fixes the one error the community directory raised against 1.0.1, and closes the gap that let it happen twice.

Requires Obsidian 1.7.2 or later, unchanged from 1.0.1. Nothing to do on upgrade.

Fixed

• The Disconnect button used setDestructive(), an API introduced in Obsidian 1.13.0, while this plugin supports 1.7.2. It now uses setWarning(), which looks identical and exists at that version.
• The connect dialog builds its code block with createDiv() instead of createEl("div", …), as Obsidian's guidelines prefer.
• manifest.json and styles.css now carry build provenance alongside main.js, so every file you install can be traced back to the workflow run and commit that produced it.

Why it needed a release at all

The obsidian package resolves to the newest typings, so TypeScript accepts any current API no matter what minAppVersion promises. It has no concept of when an API was added, which is how a 1.13.0 call shipped in a plugin declaring 1.7.2.

This release installs the ruleset the community directory itself runs and puts it in the release workflow, so a tag can no longer ship an API newer than the version it claims to support. minAppVersion: 1.7.2 is now checked rather than asserted.

Full changelog: 1.0.1...1.0.2

1.0.1

Fixes everything Obsidian's automated review flagged on 1.0.0. No behaviour changes for users, apart from two command names.

Requires Obsidian 1.7.2

Raised from 1.5.0. workspace.revealLeaf returns a promise only since 1.7.2, so the previous manifest claimed support it did not have.

Changes

• Commands renamed to Save current note and Save URL. Obsidian already shows the plugin name beside each command, so they read "Stashwise: Save current note to Stashwise".
• Deleting a note for a removed save now uses FileManager.trashFile, honouring your Obsidian "deleted files" preference rather than always using the system trash.
• The settings text reads your actual config folder instead of assuming .obsidian.
• No console logging.
• One fewer build dependency.

Plus internal type safety and API modernisation with no user-visible effect.

1.0.0

First release.

Brings your Stashwise library and wiki into your vault as real notes, lets you search them from any note, and sends what you write back.

What it does

• Sync. Saves become notes with their summary, takeaways and source. Wiki topics become their own notes, linked to related topics, so graph view shows the shape of what you have been reading.
• Search and insert. A sidebar panel and two commands drop a link or a quote callout at your cursor without leaving the note.
• Write back. Anything you type under a synced note is sent to Stashwise as your note on that item.
• Mobile. Runs on Obsidian for iOS and Android. Save in the Stashwise app, open Obsidian, the note is there.

Your writing is never overwritten

Each synced note has a region Stashwise owns, between %% stashwise:begin %% and %% stashwise:end %%. Everything below the end marker is yours and is never touched.

If those markers go missing, the plugin refuses to write to that file and tells you it skipped it, rather than guessing where your writing begins.

Install

Awaiting review for the community directory. Until it appears in Browse, install with BRAT using StashwiseAI/stashwise-obsidian, or download the three files below into .obsidian/plugins/stashwise/.

See the README for step by step instructions.

Requires

Obsidian 1.5.0 or later, and a Stashwise account. The free plan works.