Releases: enwikipedia-acc/waca
Releases · enwikipedia-acc/waca
7.5.2
Update chat link to point to Libera Chat
7.5.1
- Fix invalid dev team JSON
- Extend checks in the fast closes statistics page to check for enqueue times as well as closure times
- Add JS confirmation popup to auto-create buttons
- Automatically acknowledge failed auto-creation tasks. Requests are automatically deferred to the hospital queue anyway; requiring acknowledgement is unnecessary work.
- Stage jobqueue tasks before they can be run. This is to guarantee users time to cancel a mistaken auto-creation before it actually executes.
- Extract job queue batch size to a configuration option
- Add IRC ping for failed auto-welcome jobs
- Allow cancelling of jobqueue jobs independently. This will not move a request out of the jobqueue queue; if there are no creation jobs remaining, then the request will sit in that queue indefinitely.
- Rename the reset button to indicate that it will cancel pending jobs when in the job queue.
- Hide auto-creation buttons when a request has already had an email sent to the user. No change in functionality, just hiding an exception.
- #689 #250 Add a speed-bump when a request is marked as manually custom created, but the account doesn't actually exist
7.5
- #671 Add a Special:Globalusers link to the interface
- #624 Prevent applications with IP address as requested username
- #619 Prevent emails being sent for purged requests
- #680 Job queue should display newest first
- #617 Clean up the UX surrounding ability to reopen old/purged requests
- #690 Autofocus text cursor on TOTP field
- #684 Add new creation-type options to custom close for oauth/bot auto-creations
- #684 Allows creation tasks to bypass email-sent checks if the creation task originates from a custom close
- #684 Mark auto-creations as having had an email sent
- #684 Log custom closure text with the request
- #684 Show the email body on the jobqueue entry in case of job failure
- #656 Fix unhandled HTTP timeout during account request
- #669 Fix unhandled exception when editing a comment to an empty string
- #685 Introduce extra logging around IRC notifications with a view towards identifying underlying temperamentality
7.4.2
Security fix for Smarty (CVE-2021-26120)
7.4.1
- Don't send IRC notification for successful scheduled creations, we already send one for the enqueue
- Allow acknowledgement of jobqueue jobs by oauthcreation users
- Change autocreate failure IRC pings to mention the user who triggered the failed job
7.4
- #625 Add some protection against null JS questions on email templates
- #649 Don't flag purged email addresses as "uncommon"
- #648 Revoke any active password reset tokens on successful login
- #658 Add option to re-show the site notice once it has been dismissed.
- #659 Custom close log entries are now searchable on the Logs page
- #637 Fix unhandled exception while searching for rename logs
- #660 Include more statistics based on the statistics sent as part of the new year update
- #651 Tweaks to dark mode theme surrounding the sitenotice border and dark outline-only buttons
- #632 Allow usage of identity tickets for old OAuth consumer tokens
- #631 Add force-create button for checkusers
- #627 Add exception viewer for tool roots
7.3
- #635 XFF demo style fix for dark mode
- #638 WelcomeTemplate links point to enwiki instead of a broken path in the ACC tool due to use of relative links
- #644 Two fixes to stats pages - user non-creation stats now lists the correct set of requests, and the top creators page now links to the user stats page (fixing a newinternal regression)
- #653 Wording tweak on user statistic page
- #650 Welcome templates tidy-up:
- Fixes to parameters in templates, and associated help text.
$username
is now deprecated in Welcome Templates, please use the other less-ambiguous variables instead - Show the automatically-added header in the preview
- Show the code used in the main table (large screens only) and view page
- Fixes to parameters in templates, and associated help text.
- #654 Minor information disclosure security fix
7.2
- #633 Common email domain check is no longer case-sensitive
- #640 Fix cleanup of unconfirmed requests with comments
- #610 Fix default welcome template for new users
- #612 Fix reporting for new "created"-type close templates
- #574 Improvements to bans:
- Bans can now auto-defer a request to a different queue, automatically drop the request, or do nothing, in addition to blocking the request from being submitted
- Bans can now target a combination of attributes, such as an IP address and an email address at the same time.
- Useragent bans are now supported for CheckUsers
- Username, email, and useragent bans are now regex-aware
- IP address bans are now CIDR-aware, permitting range bans
- Ban targets now have restricted visibility
- Ban reasons can be restricted per-ban, such that only admins or only CUs can see a ban reason
- Bans now cannot be unset unless you can see the entirety of the ban
- Ban targets no longer appear in log entries. Log entries are linked to view the specific ban instead.
- #574 Comments can now be submitted with checkuser-only visibility restrictions, in addition to the existing tool admin visibility restrictions. A corresponding UI tweak has been made to support this. Comments submitted with limited visibility can always be seen by the comment author.
- #574 The minimum MariaDB version has been bumped to version 10.3.22.
7.1
- Uncommon email domains are now flagged
- Minor redesign of multiple requests from this IP/email flag
- TopCreators stats page now shows current user again
- Spaces are automatically stripped from the start and end of requested usernames
7.0.7
- Prevent non-admins from reopening purged requests
- Fix logic for <1 week request reopening