sudacode/SubMiner

Fork 0

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-08-01 19:21:34 -07:00

Files

T

History

sudacode c2781a3f80

fix(anime): retry cold upstream fetches in the stream strip proxy

Right after an episode resolves, the bridge (or the host behind it) can
error on the very first segment fetches and be fine a moment later; mpv
sweeps the playlist of failing segments in ~2s and gives up with "no
audio or video data played" while a manual reload of the same URL plays.
Retry a failed GET once after 400ms and log upstream error statuses so
the next failure names the real cause in the app log.

2026-08-01 00:24:26 -07:00

anime-browser.md

fix(anime): retry cold upstream fetches in the stream strip proxy

2026-08-01 00:24:26 -07:00

macos-yomitan-popup-passthrough.md

fix(overlay): keep Yomitan popup interactive on macOS/Windows (#177 )

2026-07-30 19:47:08 -07:00

README.md

docs(changelog): require reconciled fragments, not just new ones (#113 )

2026-06-06 00:55:34 -07:00

word-card-kind.md

feat(anki): add configurable word card type for Kiku/Lapis (#175 )

2026-07-31 17:17:29 -07:00

README.md

Changelog Fragments

Add one .md file per user-visible PR in this directory.

Use this format:

type: added
area: overlay

- Added keyboard navigation for Yomitan popups.
- Added auto-pause toggle when opening the popup.

For breaking changes, add breaking: true:

type: changed
area: config
breaking: true

- Renamed `foo.bar` to `foo.baz`.

Rules:

type required: added, changed, fixed, docs, or internal
area required: short product area like overlay, launcher, release
breaking optional: set to true to flag as a breaking change
each non-empty body line becomes a bullet
README.md is ignored by the generator
if a PR should not produce release notes, apply the skip-changelog label instead of adding a fragment

PR branch workflow:

Before adding a fragment or bullet, inspect the changes/*.md files already changed in the PR
If the new work fixes, modifies, renames, or supersedes behavior introduced or referenced by that fragment, edit or remove the stale bullet instead of adding follow-up churn
Add a new bullet only when it describes a truly separate user-visible outcome
Multiple fragment files are allowed when one PR has genuinely separate release-note outcomes, but keep them minimized and current

How fragments turn into a release:

At release time, bun run changelog:build (and bun run changelog:prerelease-notes) pipes every pending fragment through claude -p to merge related items, drop noise, and rewrite into a clean user-facing release body. Write fragments as raw, informative notes — don't worry about polished prose, deduping across PRs, or line-by-line phrasing. The polish step handles all of that.
The polish step treats pending fragments as the final release outcome, not prerelease history. If a feature is added and then renamed or fixed before the stable cut, ship the final feature bullet instead of separate prerelease-only breaking/fix entries.
GitHub release notes and prerelease notes use short top-level items with nested bullets for the change, user benefit, and any useful action note. The stable CHANGELOG.md can stay in compact single-line bullets.
internal fragments stay in CHANGELOG.md (inside a collapsed <details> block) but are dropped from the GitHub release notes entirely.
The polished CHANGELOG.md and release/release-notes.md are committed and reviewed before tagging — edit the Markdown by hand if Claude misses something.

Prerelease notes:

prerelease tags like v0.11.3-beta.1 and v0.11.3-rc.1 reuse the current pending fragments to generate release/prerelease-notes.md
existing prerelease notes are a reviewed baseline; later prerelease runs should replace stale beta/RC wording with the current outcome instead of appending fix churn
prerelease note generation does not consume fragments and does not update CHANGELOG.md or docs-site/changelog.md
the final stable release is the point where bun run changelog:build consumes fragments into the stable changelog and release notes