haskytech/retest-queue
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

feat: 0.2.1 — dual-password delete (password field) #3

Merged
haskos-bot merged 1 commit from feat/dual-password-delete into dev 2026-07-19 22:16:42 +00:00
Conversation 0 Commits 1 Files changed 4 +13 -9
john commented 2026-07-19 21:34:05 +00:00
Owner
Copy link

What

  • DeleteBugRequest.admin_password renamed to DeleteBugRequest.password
  • UI labels updated: 'Admin password' → 'Password' (since either admin or client password authorizes the delete)
  • Server-side (Python package #38) handles the dual-password matching and source attribution

Why

Operator wants to track whether admin or client initiated a bug delete. Two passwords configured server-side; the UI sends whichever password the user entered, and the server records 'admin' or 'client' as the source in the audit log.

Published

@haskytech/retest-queue@0.2.1 already published to Forgejo npm registry (manual pnpm publish, same as 0.2.0). Tag-based publish CI doesn't exist for this repo yet — tracking separately in BUG-766 Layer 2.

Spec Drift Callouts

Breaking field rename. Superclean-sys2 #397 shipped with 0.2.0 using admin_password. Need a Superclean follow-up PR to bump to 0.2.1 before this is usable end-to-end.

Tests

No new UI tests — TypeScript typecheck + eslint + build all pass. The source attribution behavior is server-side; the UI just sends the password the user typed.

## What - `DeleteBugRequest.admin_password` renamed to `DeleteBugRequest.password` - UI labels updated: 'Admin password' → 'Password' (since either admin or client password authorizes the delete) - Server-side (Python package #38) handles the dual-password matching and source attribution ## Why Operator wants to track whether admin or client initiated a bug delete. Two passwords configured server-side; the UI sends whichever password the user entered, and the server records 'admin' or 'client' as the source in the audit log. ## Published `@haskytech/retest-queue@0.2.1` already published to Forgejo npm registry (manual pnpm publish, same as 0.2.0). Tag-based publish CI doesn't exist for this repo yet — tracking separately in BUG-766 Layer 2. ## Spec Drift Callouts Breaking field rename. Superclean-sys2 #397 shipped with 0.2.0 using `admin_password`. Need a Superclean follow-up PR to bump to 0.2.1 before this is usable end-to-end. ## Tests No new UI tests — TypeScript typecheck + eslint + build all pass. The source attribution behavior is server-side; the UI just sends the password the user typed.
feat: 0.2.1 — dual-password delete (password field, no admin/client distinction in UI)
Some checks failed
CI / Backend (pull_request) Has been cancelled
Details
1acd4eb4e6 
Breaking change to DeleteBugRequest:
- admin_password: string → password: string

The UI sends a single 'password' field; the server resolves which
configured password (admin or client) matched and records the source
attribution in the audit log. UI labels updated to drop 'admin' wording
since either password can authorize the delete.

Version bump 0.2.0 → 0.2.1
haskos-bot deleted branch feat/dual-password-delete 2026-07-19 22:16:43 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
haskytech/retest-queue!3
No description provided.