docs: refresh and add showcase screenshots for v2.17.0#216
Conversation
Deploying podnotes with
|
| Latest commit: |
24fdf15
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ed5a3b70.podnotes.pages.dev |
| Branch Preview URL: | https://chhoumann-release.podnotes.pages.dev |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| [Semantic Versioning](https://semver.org/), and releases are cut automatically from | ||
| [Conventional Commits](https://www.conventionalcommits.org/). | ||
|
|
||
| ## 2.17.0 — 2026-06-22 |
There was a problem hiding this comment.
🚩 CHANGELOG documents version 2.17.0 while manifest.json is still at 2.16.0
The new CHANGELOG.md:7 header says ## 2.17.0 — 2026-06-22, but manifest.json and package.json both still show "version": "2.16.0". Per AGENTS.md, the release setup is semantic-release based and npm version runs version-bump.mjs to keep manifest.json and versions.json in sync. This is likely intentional — the changelog is being staged ahead of the automated version bump — but worth confirming that the release pipeline will actually produce 2.17.0 (not e.g. 2.16.1) given the conventional commits on the base branch. If semantic-release computes a different version, the changelog header will be wrong.
Was this helpful? React with 👍 or 👎 to provide feedback.
Refresh the showcase screenshots with realistic demo data and add new ones for the features shipping in 2.17.0: the player, a Bases-friendly episode note, clickable timestamp links, a speaker-labelled transcript, a podcast feed note, an Obsidian Bases view, and the diarization settings. Wire the new and refreshed images into the README and docs (index, templates, timestamps, transcripts). No source changes — documentation and release assets only.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b18e170ed9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| This will make PodNotes capture the current playback time to the active note, in the format given in the plugin settings. | ||
| PodNotes can also capture recent playback segments with the `Capture Last 10 Seconds` and `Capture Last 20 Seconds` commands. | ||
|
|
||
| With the default `{{linktime}}` format, each captured timestamp becomes a clickable link that reopens the episode at that exact moment: |
There was a problem hiding this comment.
For a fresh install the default setting is still DEFAULT_SETTINGS.timestamp.template = "- {{time}} " in src/constants.ts, so Capture Timestamp inserts a plain time rather than an episode link unless the user changes the format to {{linktime}}. This added sentence tells users the default capture is clickable, which will make the new screenshot/docs incorrect for the default configuration.
Useful? React with 👍 / 👎.
chhoumann
force-pushed
the
chhoumann/release
branch
from
b18e170 to
24fdf15
Compare
chhoumann
changed the title
|
🎉 This PR is included in version 2.17.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
…ages (#217) * docs: fix regressed showcase images (hero grid + episode note) Two images from #216 were downgrades and are corrected here: - podcast_grid_big.png: restore the original full library hero (the replacement showed only a handful of tiles). - podcast_note.png: re-capture the note-while-listening view as a side-by-side of a Bases-friendly episode note (with timestamp links) and the PodNotes player + queue, instead of just the properties panel. * chore(release): keep trailing newline in manifest.json and versions.json version-bump.mjs wrote both files with JSON.stringify and no trailing newline, so every release commit stripped the newline Biome expects. Because the release commit is [skip ci], format:check never ran on it, and the next unrelated PR failed format:check on manifest.json. Append a trailing newline in version-bump.mjs and restore it on both files. * ci: retrigger checks
1 participant
Refreshed and new showcase screenshots for the PodNotes 2.17.0 release, captured in a real Obsidian vault with realistic demo data (a subscribed library incl. Acquired, Huberman Lab, The Knowledge Project, etc.) and wired into the README and docs.
The benefit-led 2.17.0 changelog lives in the GitHub release body (not as a file in the repo).
Screenshots
player.png,podcast_grid.png/podcast_grid_big.png(refreshed)podcast_note.png— Bases-friendly episode note propertiestimestamps.png— notes with clickable timestamp linkstranscript_diarization.png— a transcript with speaker labelsfeed_note.png— a podcast feed notebases_view.png— an Obsidian Bases table of episode notesdiarization_settings.png— the diarization settingsDocs
Wired the new/refreshed images and feature mentions into
index.md,templates.md,timestamps.md,transcripts.md, and the README.Verification
lint,typecheck,build,test(743 passing),format:check,docs:buildall green.No source changes — documentation and release assets only.