feat: filament→spool prompt, today's purchase date, color column, cumulative changelog (v1.38.0)#58
Merged
Merged
Conversation
…ulative changelog (v1.38.0) - After registering a filament, its detail opens a modal offering to register a spool of it right away (links to New Spool with the filament preselected). - New Spool form pre-fills the purchase date with today's date (editable); no change when editing an existing spool. - Spool list gains a "Color" column: a swatch + the color name (from the filament, or the bucket derived from the hex when unnamed). - "See what's new" now shows the CUMULATIVE changelog for users several versions behind: all version sections between the installed and latest versions, sourced from CHANGELOG.md at the latest tag (raw.githubusercontent — no 60/h API limit), falling back to the latest release notes on failure. - Fix: restore the 1.36.2 CHANGELOG entry, accidentally dropped in the v1.37.0 merge (its body had leaked under the 1.37.0 section). - i18n (EN/ES) and tests for all of the above. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Four UI/UX improvements requested by the user, plus a changelog regression fix.
Changes
1. Prompt to register a spool after creating a filament
After saving a new filament, its detail page opens a modal: "Register a spool of this filament now?" → links to New Spool with the filament preselected (
/spools/new?filament_id=<id>). Mirrors the existing spool→queue prompt pattern.2. Purchase date pre-filled with today
The New Spool form now defaults Purchase date to today (server-side
date.today(), editable). Applies both to manual entry and to the flow from #1. Editing an existing spool is unchanged.3. "Color" column in the spool list
Each row shows a swatch + the color name (
color_name; when unnamed, the bucket derived from the hex viaclassify_color). Works in filtered/search views too.4. "See what's new" shows the cumulative changelog
Previously only the latest release notes. Now, for users several versions behind, it shows all version sections between the installed and latest versions, sourced from
CHANGELOG.mdat the latest tag (viaraw.githubusercontent.com— no 60/h API limit). Fail-open: on any fetch/parse failure it falls back to the previous behavior (latest release notes).Fix: restore the 1.36.2 CHANGELOG entry
While implementing #4 (which surfaces the CHANGELOG), I found the 1.36.2 entry had been accidentally dropped in the v1.37.0 merge — its body had leaked under the 1.37.0 section. Restored as its own section.
Verification
run-tests.ps1: 171 tests, all green (10 new intest_ui_v138.py: prompt redirect+modal, date default, color column + hex-bucket fallback, changelog slicing, cumulative notes + both fallbacks).CHANGELOG.mdatv1.37.0+ slicing verified end-to-end (correct version range, lower bound exclusive).Deploy
MINOR (1.37.0 → 1.38.0). After merge: create release
v1.38.0and update via/admin/update.🤖 Generated with Claude Code