Repository navigation
chore: release 0.3.0 - #32
Conversation
Three features that had not been released, and the fixes from three review passes over everything. The features: the drives that are plugged in are listed rather than found through a file dialog, tracks can be taken back out of the list one at a time, and clearing the whole list asks first. The fixes worth naming, because each was a wrong answer to the question this program exists to answer. HE-AAC was reported as playing on all ten players, having been judged against limits written for AAC-LC. A video with an AAC stream was read as a track. A drive whose tree the browser cannot reach in full was summed up as though it were whole, and folders that could not be read at all were dropped in silence. Two more destroyed files. Two inputs could claim one destination and race for it, and a source could be written over by its own conversion when the same path was spelled two ways. One made the result worse: a 128 kbps MP3 asked for cdj-safe was re-encoded at 320, which is the same music through a second encoder. The screen was rewritten around what a row needs rather than what is wrong with it, and both READMEs follow what the program now does.
|
Warning Review limit reached
Next review available in: 83 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
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. Comment |
The version, in the four places that carry it. Nothing else changes.
Cargo.tomlgui/src-tauri/tauri.conf.jsongui/package.jsonCargo.lockNo
0.2.1is left anywhere else in the tree.Minor rather than patch: three features had been sitting unreleased, and a
conversion now produces different bytes than it did — a lossy source is no
longer re-encoded above the bitrate it arrived with, and a folder handed over
whole keeps its shape under one output folder instead of growing one at every
level.
What ships
Features. The drives that are plugged in are listed rather than found
through a file dialog. Tracks can be taken back out of the list one at a time,
and clearing the whole list asks first.
Wrong answers to the question this program exists to answer. HE-AAC was
reported as playing on all ten players, having been judged against limits
written for AAC-LC. A video with an AAC stream was read as a track. A drive
whose tree the browser cannot reach in full was summed up as though it were
whole, and folders that could not be read at all were dropped in silence.
Files destroyed without a word. Two inputs could claim one destination and
race for it. A source could be written over by its own conversion when the same
path was spelled two ways —
convert track.mp3 -o .did it.Work that made the result worse. A 128 kbps MP3 asked for
cdj-safewasre-encoded at 320: the same music through a second encoder, at two and a half
times the size, replacing a file that already played everywhere.
The screen, rewritten around what a row needs doing to it rather than what
is wrong with it, and both READMEs brought in line with what the program does.
The release pipeline refuses a macOS bundle whose seal does not cover its
sidecars — the state where macOS calls the app damaged and offers only the
Trash, which nothing here would otherwise notice until somebody downloaded it.
Release notes
Generated against a throwaway tag before this was opened, because the body is
frozen when the draft is created and cannot be corrected afterwards: three
features, twenty-five fixes, one documentation entry, two refactors. The
cientries are skipped by
cliff.toml, which is right — none of them is visibleto anyone downloading this.
One thing that reads oddly and is not fixed here: the fixes are listed newest
first, so the one that matters most sits at the bottom. Changing that means
changing
sort_commitsfor every release, which is not this branch's business.After merging
v0.3.0onmain, pushed, which is what runs the release.