Repository navigation
Releases
v13.13
In short
Copy Checklist and the other destination pickers list the
cards of a large board again: a board that loads its cards lazily used to leave
the card dropdown empty. Dependabot's updates, among them i18next 27 and
the mongodb driver 7.8.0, are kept.
Thanks to above GitHub users for their contributions.
v13.12
In short
WeKan is updated to Meteor 3.6.1, whose DDP server refuses
malformed messages without stalling the connection. One shared list header
row now shows the same lists in every swimlane, scrolling together, and
Shift+M and Shift+C open Move Card and Copy Card. Those popups
remember the swimlane and list, not only the board. The embedded-engine
benchmark takes OpenTelemetry 1.47.0 for a Dependabot alert. A REST
API write that changes nothing answers 404, and a card deletion naming the
wrong list no longer strips the card's checklists (ListLockBleed).
Security
A card deletion naming another list no longer strips the card's checklists and comments. Thanks to xet7.
A follow-up to ListLockBleed,
GHSA-4734-8vrg-8j3w,
found while checking the REST deletions. DELETE /api/boards/:boardId/lists/:listId/cards/:cardId found the card by board
alone, removed its checklists, checklist items, comments and attachments, and
only then removed the card by board AND list. With the wrong list id the card
stayed, emptied, and the reply was 200. Only the list in the URL was asked
whether the caller may write, so a member a list refuses could strip the cards
of that list by naming one they may write. The card now has to be in the named
list, its own list is asked as well, and the refusal shows in Admin Panel /
Problems as authz.list-locked. tests/restWriteRoutes404.test.cjs runs the
handler on both cases and requires the list check before anything is removed,
and tests/playwright/specs/rest-write-routes-404.e2e.js checks that the
checklist survives against a running server.
Thanks to above GitHub users for their contributions.
v13.11
In short
The file-integrity scan stops reporting attachments and
avatars that WeKan deleted itself as missing, which had buried real
StorageBleed findings under thousands of false ones. The recurring-checklist
reset no longer scans every checklist on each tick. In the REST API, a
refused custom-field update changes nothing, ownership transfer takes only the
boards the user administers, and deleting a missing integration answers 404.
Thanks to above GitHub users for their contributions.
v13.10
In short
The release's Snap Store credential check bounds each
snapcraft install attempt, so a Snap Store that hangs no longer stops a release.
Thanks to above GitHub users for their contributions.
v13.09
In short
The release's Snap Store credential check retries installing
snapcraft, so one Snap Store timeout no longer stops a release.
Thanks to above GitHub users for their contributions.
v13.08
In short
The REST API creates a card under the parent it is given,
and a refused integration URL no longer leaves the other fields of the same
update written. The single-file WeKan for 32-bit ARM builds again, with
an i386 Node.js of the exact version its bundle embeds. A GitHub CodeQL
alert in the security alert download script is fixed.
Thanks to above GitHub users for their contributions.
v13.07
In short
ListLockAttachBleed is fixed: when a list refuses a role
write access, that refusal now also holds for the attachment API's upload,
delete, copy and move. CodeQL alerts #602 and #603 in the tests are fixed,
fast-xml-parser is updated to 5.12.0, spent time reads as a duration,
the indexes that LDAP, card member and History queries need are added, and
Admin Panel → Problems can Clear resolved problems, which also age out.
Security
A list that refuses a role write access refuses its attachment API writes too. Thanks to Furkan Derse and xet7.
ListLockAttachBleed,
reported by email, its GitHub security advisory awaited. A board admin can
refuse a role write access in one list (#4527). The card screen, the card and
checklist routes (ListLockBleed)
and the interface's own attachment upload and delete applied that refusal, but
the attachment API's upload, delete, copy and move, over REST and DDP, asked
only for board write access and the assigned-only rule. A normal member the
list refused could therefore still add and remove files on its cards. Every
attachment write that names a card now asks that card's list as well, a move
both the card it takes the file from and the one it puts it on, and the
refusal shows in Admin Panel / Problems. tests/listLockAttachments.test.cjs
runs the guard on the reported case and fails on any attachment write in the
tree without the list check beside it, and
tests/playwright/specs/list-lock-attachments.e2e.js replays the writes
against a running server.
Thanks to above GitHub users for their contributions.
v13.06
In short
CodeQL alert #601 in a test is fixed, with two more tests
that had the same fault. A card's overtime set through the REST API is
saved where WeKan reads it, and cards that lost it before are repaired at
startup. Card members and assignees whose account was deleted can be removed
and added without an error, and clearing a card date no longer passes as a
date set to the rules, the due date count and the activity feed.
Thanks to above GitHub users for their contributions.
v13.05
In short
WeKan is updated to Meteor 3.6. The Android bundles
build again, after v13.04's npm retry broke their install, and the Super
Productivity export no longer fails for a board with a card whose list is
archived.
Thanks to above GitHub users for their contributions.
v13.04
In short
ListLockBleed is fixed: when a list refuses a role write
access, that refusal now also holds for the checklist and checklist-item REST
routes. The Sandstorm and Android bundles retry their npm install when
github.com is briefly unavailable.
Security
A list that refuses a role write access refuses its checklist REST writes too. Thanks to tsurutanmen and xet7.
ListLockBleed,
GHSA-4734-8vrg-8j3w.
A board admin can refuse a role write access in one list (#4527). The card
and comment REST routes and the DDP checklist writes applied that refusal,
but the six checklist and checklist-item REST routes asked only the board. A
member the list refused could therefore still create, rename, tick and delete
the checklists of its cards with an API token. Those routes now ask the
card's list and answer 403, and the refusal shows in Admin Panel / Problems.
tests/listPermissions.test.cjs fails for any REST write route of the tree
that names a card without asking its list. And
tests/playwright/specs/list-lock-checklists.e2e.js replays the six writes
against a running server.
Thanks to above GitHub users for their contributions.