Repository navigation
release: tiger-core 1.42.0 - #367
Merged
Merged
Conversation
…grid on /api (TIGER-383), UI test harness (TIGER-386) Minor, not patch: three new @api methods ship (Tiger_Service_Authentication:: resetTokenIsLive, Tiger_Model_UpdateHistory::datatable, System_Service_Updates:: datatable). No breaking changes — System_Service_Updates::history() is kept for API/MCP callers, and the reset submit path is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013vdyTeoDrGE4hKxt53TsE8
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.
Version bump + changelog for 1.42.0. Code already merged via #365, #366, #364.
Minor, not patch — three new
@apimethods ship:Tiger_Service_Authentication::resetTokenIsLive()Tiger_Model_UpdateHistory::datatable()System_Service_Updates::datatable()No breaking changes.
System_Service_Updates::history()is kept for API/MCP callers, and the reset submit path is untouched.What's in it
Fixed — a dead password-reset link now says so before you choose a password (TIGER-387). An expired or already-used link used to render an ordinary "Set a new password" screen; the user typed a password twice and only then learned the link was dead. The refusal was always safe — it just arrived after the work, to people already locked out.
Changed — the Updates history is a real grid fetched from
/api(TIGER-383). The one admin screen still server-rendering list data. Behind the consistency point was a real gap: only the newest 15 runs were ever reachable.Added — the functional UI test harness (TIGER-386). The thing that found both of the above. Its first scan over 108 view scripts reported zero page-POST violations, so the client/server paradigm holds across the codebase.
Verification
CAPABILITIES.mdcurrentOn merge, pushing
v1.42.0triggersrelease-zip.yml: tag-format gate → smoke matrix on the exact tag → vendored ZIP built and attached to the published Release, which is whatTiger_Update_Coredownloads.🤖 Generated with Claude Code
https://claude.ai/code/session_013vdyTeoDrGE4hKxt53TsE8