Repository navigation
·
2 commits
to development
since this release
Features
- disable Grade C reindex while rows are selected and add tooltips for disabled actions (#323)
- replace Grade C upload file input with a read-only file row and reset delete toggle on file change (#312)
- show Grade C indicators with their units in dataset details (#320)
- show indicators summary and drop excluded regional values in Grade C details (#300)
- show loading toast while Grade C datasets are being deleted (#303)
- show n/a for empty Grade C dataset fields and hide empty missing indicators (#309)
- support per-stage force and indicator summarization in Grade C reindexing (#317)
Fixes
- add hover effect to close button in modals (#314)
- apply audit log column filters to export (#313)
- bump follow-redirects override to 1.16.2 (#322)
- keep upload modal height fixed across all steps (#318)
- keep upload modal size stable while a file is uploading (#316)
- refresh the session and retry on 401 instead of failing with "Could not validate credentials" (#301)
- rename Grade C export button to "Export dataset" (#310)
- replace Grade C upload confirm step with inline warning and file error state (#311)
- reset stale grade c enum filters after deleting records (#302)
CI
- move SCA scan to its shared cron slot (#308)
Other
- (deps) patch minimatch and glob advisories and drop redundant overrides (#326)
- bump next from 16.4.3 to 16.4.6 in the security-updates group across 1 directory (#325)
- override smol-toml to fix high-severity DoS vulnerability (#262)
- update ai-dial-ci version (4.5.0 -> 4.13.2) (#307)
Deployment changes
Backend compatibility
Important
Grade C reindexing now sends force as repeated stage parameters (e.g. ?force=summarization&force=publishing) and the details view expects indicatorsSummary. Deploy together with the matching statgpt-backend release: a backend without per-stage force rejects the request (422), and one without the separate indicator sheets template (statgpt-backend#764) will not return the new fields (#317, #300).
Behavioral changes
Note
After redeploying, expired access tokens are refreshed and the request retried automatically; users whose refresh token is invalid are redirected to sign-in.
- Session refresh — refresh happens shortly before token expiry (60 s, capped at 20% of the token lifetime) and
invalid_grantis treated as terminal (#301)