Repository navigation
Release v0.3.0 - #340
Merged
Merged
Release v0.3.0#340
Conversation
The first release with the rebuilt control panel (#326): five hairline-separated columns in place of five bordered boxes of equal weight, a mode rail with the view controls in its foot, a permanent collapsible guidance column, instrument-styled readouts with frequency as the one lit reading, a twin-tab style panel that states its target, reversed-out selected rows, the selected feature haloed on the gram, and a transport bar with time bookmarks. What an analyst sees and reaches for changes more than in any release since the player, so a minor bump, as v0.2.0 was for region zoom and the player refinements. v0.2.1 is the last release with the legacy panel and stays published. Config tables and annotation storage are unchanged between the two. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CrHtVussSR8ZxsxisaepJM
Contributor
PR PreviewPreview deployment is ready! View Preview Last updated: 2026-09-18T10:25:48.868Z |
The v0.2.1 release run failed on AS-4.3 in tests/player-annotations.spec.js with the marker measured hundreds of pixels from where the seek should have put it, while the same commit passed the Tests workflow on main and passes the spec repeatedly here. The seek redraws synchronously, but the media element's own `seeked` event redraws again a moment later, and a single bounding-box read landing between the state settling and that redraw sees a stale position. Poll it, as the suite does elsewhere, so the assertion waits for the drawing rather than racing it. The release gate is the same suite, so this rides the release PR. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CrHtVussSR8ZxsxisaepJM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two commits: the version bump, and one test made robust because the release gate flaked on it.
Release v0.3.0
package.json0.2.1 → 0.3.0, following the pattern of #339. Once merged, tagging the merge commitv0.3.0runs the release workflow and publishes the bundle.Why a minor bump
The first release with the rebuilt control panel (#326). The upper panel is five hairline-separated columns instead of five bordered boxes of equal weight, and what an analyst sees and reaches for changes more than in any release since the player. v0.2.1 is the last release with the legacy panel and stays published for any publication that needs it.
Since v0.2.1
B) flags the playhead, flags jump, the saved list removes; playback chrome, never annotation dataCompatibility
core/preferences.js); absent under legacy, harmless thereThe test made robust
The v0.2.1 release run failed on
tests/player-annotations.spec.js› AS-4.3 with the marker measured hundreds of pixels from where the seek should have put it, while the same commit passed the Tests workflow on main and passes the spec repeatedly locally (three of three, then two of two with the change). The seek redraws synchronously, but the media element's ownseekedevent redraws again a moment later, and a single bounding-box read landing between the state settling and that redraw sees a stale position. The assertion now polls, as the suite does elsewhere. The release gate is the same suite, so this rides the release PR rather than waiting for the v0.3.0 tag to meet it.Checks
yarn typecheck,yarn lint,yarn hygiene— cleanyarn test:unit— 348 passedtests/player-annotations.spec.jswith the change — 18 passed over two repeats🤖 Generated with Claude Code
https://claude.ai/code/session_01CrHtVussSR8ZxsxisaepJM