Fix #49: new-release section redesign #60
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!60
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-49"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Redesigns the new-release composer (web/src/pages/ReleaseNew.jsx) so it is no longer a bare box adrift in whitespace: centered max-w-2xl column per the IssueNew/PullNew convention, heading row with an all-releases back link, Target/Content/Visibility fieldsets with per-field help text, the tag datalist picker kept (fed by tags({n:100})) plus a tag-count/empty/loading line, title placeholder defaulting to the typed tag, draft/prerelease as bordered checkbox option rows with descriptions, an action row (primary create + secondary autodraft with busy labels, post-creation asset-upload note), and an inline role=alert error line instead of a native required bubble. All behaviors kept: autodraft fill (body/since/name), create-to-detail navigation, busy/disabled logic; assets stay on the detail page. No backend/SDK change, no new deps. Decision appended to docs/go/12_web_ui.md.
Verification: node --test web/test/unit/*.test.js 245/245 green; real-browser CDP drive (headless Chrome :9222) against a scratch zero-config server with a 2-tag repo — 16/16 checks (empty + validation + filled + submitted, dark + light, zero console/page errors).