Compare commits

..
34 Commits
Author SHA1 Message Date
github-actions[bot] 7347ae8f9d Bump versions for v13.09 2026-11-12 19:07:47 +00:00
Lauri Ojansivu 6cbb026f14 Prepare v13.09 release 2026-11-12 21:06:44 +02:00
Lauri Ojansivu 80253cf5e1 Merge remote-tracking branch 'origin/main' 2026-11-12 21:06:21 +02:00
Lauri Ojansivu d8fc23a4f4 CHANGELOG: snap-auth-check retries installing snapcraft.
Thanks to xet7 !
2026-11-12 21:02:13 +02:00
Lauri Ojansivu 534646347c Release: snap-auth-check retries installing snapcraft, as the build job does.
The v13.08 release stopped in snap-auth-check before it asked the Snap Store
anything: "cannot install system snap snapd: Post
https://api.snapcraft.io/v2/snaps/refresh: ... Client.Timeout exceeded while
awaiting headers". The job installed snapcraft once, while the snap build
job already retried five times, 30 seconds apart. It retries the same way now,
and when every attempt fails it says the store did not answer - not that
SNAP_AUTH is wrong.

tests/snapAuthPreflight.test.cjs fails on any snapcraft install in any
workflow without the five-attempt retry, and on the outage being reported as
a credential problem.

Thanks to xet7 !
2026-11-12 21:01:37 +02:00
github-actions[bot] 779ba553ce Bump versions for v13.08 2026-11-12 17:15:00 +00:00
Lauri Ojansivu 3144a578b5 Prepare v13.08 release 2026-11-12 19:13:48 +02:00
Lauri Ojansivu 82a30561d7 CHANGELOG: list-sync-estimate's checkbox test and index order.
Thanks to xet7 !
2026-11-12 17:03:34 +02:00
Lauri Ojansivu af76406d12 Tests: list-sync-estimate's checkbox test no longer depends on index order.
"dotted checkbox writes emit false once and removing a valued field emits an
unset" read the card's activities with an unsorted find and expected them in
insertion order. On FerretDB with the pushdown of plain equality, that find is
served by activities' { cardId: 1, createdAt: -1 } index and returns the newest
first, so it failed every time against Weddy, which creates WeKan's indexes,
with ['unsetCustomField', 'setCustomField']. The order of an unsorted find is
no contract on MongoDB either once an index serves it; what the test pins is
one set and one unset, so it now compares the activity types sorted.

Thanks to xet7 !
2026-11-12 17:03:33 +02:00
Lauri Ojansivu f57ea060fe CHANGELOG: CodeQL alert 604 in the security alert download script.
Thanks to GitHub CodeQL and xet7 !
2026-11-12 16:07:40 +02:00
Lauri Ojansivu ed19817433 releases/sec: SUMMARY.md carries no secret scanning field, and kept secrets are owner-only.
Code scanning alert #604 (py/clear-text-storage-sensitive-data, CWE-312):
download_github_security.py wrote a secret scanning alert's
secret_type_display_name into SUMMARY.md. That is the secret's type, not the
secret, but SUMMARY.md is the one file that is never redacted and the one most
likely to be pasted somewhere, so it now says only "Secret scanning alert" and
points at secret-scanning/, where the type still is. When
--include-secret-values keeps the secrets, the files holding them are created
readable by their owner only.

tests/securityDownloadScript.test.cjs checks the summary of a redacted and of a
kept download for the secret, its type and its type name, the 0600 mode of
kept secrets, and that describe() reads no field of a secret scanning alert
and every secret scanning write passes the private flag.

Thanks to GitHub CodeQL and xet7 !
2026-11-12 16:07:39 +02:00
Lauri Ojansivu 2b897dbf63 CHANGELOG: REST card parent, integration URL validation, and the single-file 32-bit host Node.js.
Thanks to AhmedLukman and xet7 !
2026-11-12 16:06:09 +02:00
Lauri Ojansivu c35c672ffb Single-file: the 32-bit host Node.js is the target bundle's exact version.
The v13.07 single files for armhf, armv6 and armv7 all stopped on "The
bundle's Node.js is v26.13.0 but this is v26.13.1: a single executable must
be built by the same Node.js version it embeds." A 32-bit target's SEA blob is
written by a 32-bit Node.js, and the workflow borrowed the i386 bundle's.
Every bundle takes the newest Node.js of the pinned major its platform has, so
i386 had v26.13.1 from wekan/node-patches while 32-bit ARM still had v26.13.0.

The host is now resolved with releases/resolve-node-source.sh at the target
bundle's exact version, checked against its published SHA256, and refused
unless it reports that version. libatomic1:i386, which the bundle used to
supply in node-runtime/, comes from apt, so HOST_LIBS is gone.

tests/singleFile.test.cjs pins the exact version, the checksum before the
first run, and that the host is never taken from another platform's bundle.

Thanks to xet7 !
2026-11-12 16:05:46 +02:00
Lauri Ojansivu 642ba6e876 Merge pull request #6895 from AhmedLukman/codex/fix-integration-update-validation
Validate integration URLs before updating other fields
2026-11-12 15:59:53 +02:00
Lauri Ojansivu e9c5aa2cae Merge pull request #6894 from AhmedLukman/codex/fix-rest-card-parent
Fix parent assignment when creating cards through REST
2026-11-12 15:59:37 +02:00
Ahmed Lukman 1418cb8480 Validate integration URLs before updating other fields 2026-11-12 13:21:00 +03:00
Ahmed Lukman 552950ed63 Fix parent assignment when creating cards through REST
Read parentId from the request body so single-card creation validates and persists the requested parent, matching the bulk endpoint. Cover persistence, subtask rendering, empty parents and rejected creation requests.
2026-11-12 12:48:09 +03:00
github-actions[bot] e1e0006a35 Bump versions for v13.07 2026-11-12 06:34:24 +00:00
Lauri Ojansivu 6f23e187ab Prepare v13.07 release 2026-11-12 07:15:19 +02:00
Lauri Ojansivu ab8c3452a8 CHANGELOG: Admin Panel Problems Clear button and event retention.
Thanks to Raymond-Voogt and xet7 !
2026-11-11 22:30:06 +02:00
Lauri Ojansivu fefabbf113 Admin Panel Problems: a Clear button, and resolved problems age out.
The problem streams were append-only and Acknowledge only reset the "new"
count, so a problem fixed long ago stayed in the table and buried the live
ones. Clear, beside Acknowledge, calls the admin-only clearEventLog, which
deletes the checked streams' events up to now and stamps the
acknowledgement; anything that happens after the click shows as new again,
and an unknown stream clears nothing. A daily sweep, claimed once per
installation, deletes events older than EVENTLOG_RETENTION_DAYS (default 90,
0 keeps them forever); a recurring problem's folded row keeps a recent date,
so it stays. The setting is listed on every platform, and clear-problems is
translated to every language.

Thanks to Raymond-Voogt and xet7 !

Fixes #6893,
2026-11-11 22:29:01 +02:00
Lauri Ojansivu 50ecd8944f CHANGELOG: ListLockAttachBleed, spent time as a duration, REST token deletion and the missing indexes.
Thanks to Furkan Derse, brlin-tw, AhmedLukman, Raymond-Voogt and xet7 !
2026-11-11 21:05:44 +02:00
Lauri Ojansivu 7bb3e13ba9 ListLockAttachBleed: a list's write refusal covers the attachment API.
A board admin can refuse a role write access in one list (#4527,
roleExceptions). The attachment API's upload, delete, copy and move, over
REST and DDP, asked only for board write access and mayWriteCardAttachment,
which allows every card to a member who is not assigned-only, so a normal
member the list refused still added and removed files on that list's cards.

Every attachment write that names a card now also asks mayWriteInCardList
with that card, and a move asks both the card it takes the file from and the
card it puts it on. The card's own board decides. As for the REST card
routes, only a list's refusal counts. A refusal is recorded in Admin Panel ->
Problems as ListLockAttachBleed (authz.list-locked-attachment, medium).

tests/listLockAttachments.test.cjs runs the guard on the reported case and
the negative cases, and fails on any mayWriteCardAttachment call in the tree
without the list check beside it; list-lock-attachments.e2e.js replays the
writes against a running server.

Thanks to Furkan Derse and xet7 !
2026-11-11 20:58:01 +02:00
Lauri Ojansivu 8dc77a89d8 Indexes for the LDAP id, cards' assignees and members, and History by entity and hash.
On a large installation the database-problems page filled with collection
scans of queries WeKan makes constantly but never indexed: a user looked
up by services.ldap.id at every LDAP login and sync pass (13,000+ users,
~430 ms per login), cards by assignees or members across every board for
My Cards and the filters (1.1M cards, 1-3.7 s, dozens of times a minute),
and changeHistory by entity and by integrity hash (120,000+ rows, and
growing). Each now has an index, created at startup with ensureIndex like
every other one: services.ldap.id sparse, assignees and members both so
their $or uses an index on each branch, and changeHistory's
{ entityType, entityId, createdAt } and { integrityHash }.

Thanks to Raymond-Voogt and xet7 !

Fixes #6892.
2026-11-11 20:29:31 +02:00
Lauri Ojansivu 9f5ab97a3c Spent time: the formatter imported as cardTime.js's other dependencies are.
A require() line stayed in the script tests/acceptedFixesLogic.test.cjs
evaluates, which strips imports, and failed it.

Thanks to brlin-tw and xet7 !
2026-11-11 20:29:31 +02:00
Lauri Ojansivu 3e8e8039ff Spent time is shown as a duration, not decimal hours.
A card's Spent time is stored in decimal hours, and a Pomodoro or Flowtime
session adds its duration to it, so a short session left a badge such as
0.034722222222222224. The badge shows days, hours, minutes and seconds now,
the leading zero units left out (12h34m56s, 2m5s), and the tooltip that
names hours rounds them to two decimals. The stored value and the edit
popup keep their hours. models/lib/spentTimeFormat.js, with a unit test
and a UI test.

Thanks to brlin-tw and xet7 !

Fixes #6890.
2026-11-11 20:20:55 +02:00
Lauri Ojansivu 4bdbded5d9 Merge remote-tracking branch 'origin/main' 2026-11-11 20:13:29 +02:00
Lauri Ojansivu dce58125c9 Merge pull request #6891 from AhmedLukman/codex/fix-rest-token-revocation
Await REST token deletion before reporting success
2026-11-11 19:54:56 +02:00
Ahmed Lukman fd59a8ff70 Await REST token deletion before reporting success
Wait for Accounts.destroyToken to finish so deletion completes before a success response and rejected database writes reach the existing error handler.

Add regression coverage for delayed and failed deletion, authorization, existing token input behavior, session isolation and browser logout.
2026-11-11 14:43:56 +03:00
Lauri Ojansivu 14a2fa9f43 CHANGELOG: releases/sec's GitHub security alert download script.
Thanks to xet7 !
2026-11-11 04:26:44 +02:00
Lauri Ojansivu 801f8956fe releases/sec: download a GitHub organization's Security and quality alerts with gh.
releases/sec/download-github-security.sh ORGANIZATION saves, for every
repository of the organization (or the ones named with --repo), its
Dependabot, code scanning, secret scanning and security advisory alerts
to .tools/log/sec/<organization>/<repository>/<YYYY-MM-DD_HH-MM-SS>/,
a directory per kind: alerts.json, a file per alert, an open code
scanning alert's instances, and SUMMARY.md with every open alert and its
link. It runs the GitHub CLI outside the editor's sandbox, where gh and
its login are, so the alerts can then be read and fixed from the files
inside it. A kind GitHub does not answer - not enabled, or not visible
to the account - gets status.txt with the reason and the run goes on;
archived repositories and forks are skipped unless asked for; the secret
a secret scanning alert found is redacted unless --include-secret-values
is given. A name that is not a GitHub name is refused before it becomes
a path or an API address. .tools/ keeps the downloads out of git.

tests/securityDownloadScript.test.cjs runs it against a stand-in gh: the
layout, both pages of a paginated answer, the summary, a disabled kind,
the redaction everywhere in the download and, as negatives, bad names,
no gh and gh signed out writing nothing. buildScriptParity knows why
build.sh has no menu entry for it.

Thanks to xet7 !
2026-11-11 04:25:18 +02:00
Lauri Ojansivu 4335614dcb CHANGELOG: CodeQL alerts #602 and #603 in the tests, and fast-xml-parser 5.12.0 for Dependabot alert #188.
Thanks to GitHub CodeQL, dependabot and xet7 !
2026-11-11 03:44:57 +02:00
Lauri Ojansivu a76a19058a Updated fast-xml-parser to 5.12.0, Dependabot alert #188.
fast-xml-parser <= 5.11.2, with its stopNodes option, rescanned the rest
of the input from every "<" of a stop node's body when no ">" followed,
so n such fragments cost O(n^2) CPU before it gave up (CWE-407). The
Azure and Google Cloud storage clients bring it in; each allows 5.x, so
the lock moves to 5.12.0 - which stops at the first failed scan - with
is-unsafe 2.0.3 and strnum 2.5.1, and no override.

tests/dependencySecurityUpdates.test.cjs pins that no tracked lockfile
resolves a version below 5.12.0, with a negative that the finder flags
5.11.2 at any depth, and runs the alert's input: 40,000 unterminated
fragments in a stop node are refused within two seconds. On 5.11.2 that
input grows quadratically (20,000 fragments took 1.2 s here, so 40,000
take about 5 s); on 5.12.0 it takes about a millisecond. A dependency
inside a storage client is not an attempt anybody makes, so there is
nothing to record in Admin Panel -> Problems.

Thanks to dependabot and xet7 !
2026-11-11 03:44:13 +02:00
Lauri Ojansivu 2b65b713a0 Tests: no path handed to a shell at all, CodeQL alerts #602 and #603.
The fix for #601 passed the paths to `bash -c` as arguments ("$1",
"$2") instead of pasting them into the script. That is safe in itself,
but it still hands a temporary or checkout path to a shell, and CodeQL
flagged js/shell-command-injection-from-environment again on the two
umask tests in tests/releaseDownloads.test.cjs. Those tests no longer
use a shell: fetch.sh runs as bash's program with its arguments, the
umask is set on the test's own process around the call and put back,
and `chmod +x` is fs.chmodSync. tests/macosSandbox.test.cjs, fixed the
same way for #601, now runs ls and touch as programs of sandbox-exec,
each path an argument.

The guard (tests/testShellPathsFromEnv.test.cjs) now also refuses any
value given to a shell's -c script as an argument - spawned or as a
wrapper's program - and the one other test that did so,
tests/dbConformanceWiring.test.cjs, passes its value in the environment.
Run against the files as they were, it names all three; its pattern
takes a backslash only as an escape, so a long file cannot make it
backtrack.

The findings were in tests, not in WeKan, so there is no attempt to
show in Admin Panel -> Problems.

Thanks to GitHub CodeQL and xet7 !
2026-11-11 03:44:13 +02:00
338 changed files with 2996 additions and 2428 deletions

No files matched your search

+1 -2
View File
@@ -1,4 +1,3 @@
* text=auto eol=lf
*.{cmd,[cC][mM][dD]} text eol=crlf
*.{bat,[bB][aA][tT]} text eol=crlf
.gitea/CODEOWNERS linguist-detectable=false
*.{bat,[bB][aA][tT]} text eol=crlf
-3
View File
@@ -1,3 +0,0 @@
# Pull requests request review from the eligible staff team(s).
# One approval from either an Admin or Developer satisfies branch protection.
* @trueog/Admins @trueog/Developers
+13 -1
View File
@@ -4557,7 +4557,19 @@ jobs:
;;
esac
sudo snap install snapcraft --classic
# The Snap Store has bad minutes - a rate limit, or (v13.07) a refresh
# that timed out - so the install is retried as the build job's is;
# an outage is said as one, not as a broken credential.
installed=""
for i in 1 2 3 4 5; do
if sudo snap install snapcraft --classic; then installed=1; break; fi
echo "snapcraft install attempt $i/5 failed (Snap Store unreachable or throttling); retrying in 30s..."
sleep 30
done
if [ -z "$installed" ]; then
echo "::error::snapcraft could not be installed after 5 attempts: the Snap Store did not answer. That is the store, not SNAP_AUTH - re-run the job."
exit 1
fi
# whoami writes its answer to stdout and its complaint to stderr; both
# matter, so both are captured.
+33 -18
View File
@@ -150,27 +150,46 @@ jobs:
node-version: ${{ steps.fetch.outputs.node_version }}
# A 32-bit target's SEA blob must be written by a 32-bit Node.js: the blob
# stores its lengths as size_t (build.mjs refuses otherwise). The i386
# bundle's Node.js, of the same version, writes it for every 32-bit
# target - win32, i386 and 32-bit ARM read the same little-endian format.
# stores its lengths as size_t (build.mjs refuses otherwise). An i386
# Node.js writes it for every 32-bit target - win32, i386 and 32-bit ARM
# read the same little-endian format - but it has to be the SAME VERSION
# the target's bundle embeds (build.mjs checks that too). v13.07 took the
# i386 bundle's own Node.js, and the bundles resolve the newest Node.js of
# the pinned major per platform: i386 got v26.13.1 while 32-bit ARM still
# had v26.13.0, and armhf, armv6 and armv7 all stopped on "The bundle's
# Node.js is v26.13.0 but this is v26.13.1". So the host is resolved at
# the target bundle's exact version, from the same three sources and with
# the same published SHA256 as a bundle's Node.js.
- name: A 32-bit Node.js to build a 32-bit target
id: host32
if: steps.fetch.outputs.skip != 'true' && contains(fromJSON('["win32","i386","armv7","armhf","armv6"]'), matrix.target)
env:
GH_TOKEN: ${{ github.token }}
VERSION: ${{ steps.fetch.outputs.version }}
NODE_VERSION: ${{ steps.fetch.outputs.node_version }}
run: |
set -euo pipefail
zip="wekan-${VERSION}-i386.zip"
mkdir -p host32
gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --pattern "$zip" --pattern "$zip.sha256sum" --dir host32 \
|| { echo "::error::$TARGET needs the i386 bundle's Node.js to build, and $TAG has no $zip."; exit 1; }
(cd host32 && sha256sum -c "$zip.sha256sum" && unzip -q "$zip" 'bundle/node' 'bundle/node-runtime/*' && rm -f "$zip")
mkdir -p host32 .tools/tmp
export TMPDIR="$PWD/.tools/tmp"
rc=0
src="$(bash releases/resolve-node-source.sh i386 "$NODE_VERSION")" || rc=$?
[ "$rc" = 0 ] || { echo "::error::$TARGET needs an i386 Node.js $NODE_VERSION to build its single file, and none of the three Node.js sources has one."; exit 1; }
node_url="$(printf '%s\n' "$src" | sed -n 's/^node_url=//p')"
node_kind="$(printf '%s\n' "$src" | sed -n 's/^node_kind=//p')"
node_member="$(printf '%s\n' "$src" | sed -n 's/^node_member=//p')"
node_sha256="$(printf '%s\n' "$src" | sed -n 's/^node_sha256=//p')"
bash releases/fetch.sh -o host32/download "$node_url"
echo "$node_sha256 host32/download" | sha256sum -c -
case "$node_kind" in
binary) mv host32/download host32/node ;;
tar.xz) tar -xJf host32/download -C host32 "$node_member" && mv "host32/$node_member" host32/node && rm -f host32/download ;;
*) echo "::error::An i386 Node.js comes as a binary or a tar.xz, not $node_kind."; exit 1 ;;
esac
chmod +x host32/node
sudo dpkg --add-architecture i386
sudo apt-get update -qq
sudo apt-get install -y -qq libc6:i386 libstdc++6:i386 >/dev/null
host="$PWD/host32/bundle/node"
[ -d host32/bundle/node-runtime ] && echo "libs=$PWD/host32/bundle/node-runtime" >> "$GITHUB_OUTPUT"
sudo apt-get install -y -qq libc6:i386 libstdc++6:i386 libatomic1:i386 >/dev/null
host="$PWD/host32/node"
got="$("$host" -p process.version)"
[ "$got" = "$NODE_VERSION" ] || { echo "::error::The i386 Node.js resolved for $NODE_VERSION reports $got."; exit 1; }
echo "node=$host" >> "$GITHUB_OUTPUT"
# A 32-bit ELF target's blob is injected in a 64-bit process, by
# LIEF 1.0.0 - the version Node.js vendors - not inside this 32-bit
@@ -187,20 +206,16 @@ jobs:
env:
VERSION: ${{ steps.fetch.outputs.version }}
HOST_NODE: ${{ steps.host32.outputs.node }}
HOST_LIBS: ${{ steps.host32.outputs.libs }}
SEA_PYTHON: ${{ steps.host32.outputs.python }}
run: |
set -euo pipefail
case "$TARGET" in win*) ext=.exe ;; *) ext= ;; esac
out="wekan-${VERSION}-${TARGET}-single-file${ext}"
# The i386 Node.js finds its own libraries; the libraries are ignored by
# the x64 Node.js that runs build.mjs (another architecture).
# Exit 3: this Node.js is one LIEF cannot inject the SEA into
# correctly (releases/single-file/sea-inject.mjs says which and why).
# That is a missing single file, not a failed release.
rc=0
LD_LIBRARY_PATH="${HOST_LIBS:-${LD_LIBRARY_PATH:-}}" \
node releases/single-file/build.mjs --bundle bundle --target "$TARGET" --version "$VERSION" --out "$out" \
node releases/single-file/build.mjs --bundle bundle --target "$TARGET" --version "$VERSION" --out "$out" \
${HOST_NODE:+--host-node "$HOST_NODE"} 2> build.err || rc=$?
cat build.err >&2
rm -rf bundle
-5
View File
@@ -126,8 +126,3 @@ mongo-tools-patches/
# Generated on the Windows single-EXE runner (releases/append-windows-payload.mjs --manifest)
wekan-real-files.h
# TrueOG: never track .env files
.env
*.env
.env.*
+253
View File
@@ -124,6 +124,259 @@ its reason.
</details>
# v13.09 2026-11-12 WeKan ® release
**In short:** The release's **Snap Store** credential check retries installing
snapcraft, so one Snap Store timeout no longer stops a release.
This release has the following developer-tooling fix:
**Release builds** - the snap jobs.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/534646347c4b6467f539cb01171487d27fc7ddc7">snap-auth-check retries installing snapcraft, as the snap build job does</a>. Thanks to xet7.</summary>
The v13.08 release stopped in snap-auth-check before it asked the Snap Store
anything: the one `snap install snapcraft` timed out reaching api.snapcraft.io,
while the snap build job already retried five times. The check retries the
same way now, and when every attempt fails it says the store did not answer
rather than that SNAP_AUTH is wrong. `tests/snapAuthPreflight.test.cjs` fails on
any snapcraft install in any workflow without the retry.
</details>
Thanks to above GitHub users for their contributions and translators for their translations.
# v13.08 2026-11-12 WeKan ® release
**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.
This release fixes the following SECURITY ISSUES found by GitHub CodeQL code scanning:
<details>
<summary><a href="https://github.com/wekan/wekan/commit/ed19817433e14ef4f8cb7d9623f5d8b84a1794ff">The security alert download summary carries no secret scanning field, and kept secrets are owner-only</a>. Thanks to GitHub CodeQL and xet7.</summary>
Code scanning alert #604 (`py/clear-text-storage-sensitive-data`, CWE-312):
`releases/sec/download_github_security.py` wrote a secret scanning alert's type
name into `SUMMARY.md`. That was the type of the secret, not the secret, but
`SUMMARY.md` is never redacted, so it now names only the kind of finding and
points at `secret-scanning/`. With `--include-secret-values` the files that hold
the secrets are created readable by their owner only.
`tests/securityDownloadScript.test.cjs` pins both, and that no secret scanning
field reaches the summary. This is a maintainer tool, not WeKan's server, so
there is no attempt for Admin Panel → Problems to record.
</details>
and fixes the following bugs:
**The REST API** - creating cards and updating integrations.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/552950ed637d6ddeb486322e3c08dd61dbfc13dc">A card created with a parentId is created under that parent</a>. Thanks to AhmedLukman and xet7.</summary>
`POST /api/boards/:boardId/lists/:listId/cards` read `parentId` from the URL
parameters, which that route does not have, so the parent in the request body
was ignored: it was never stored, and the visibility check for the parent
(GHSA-jvv9-498p-hxrg) never saw it. It is read from the body now, as the bulk
endpoint does. A parentId that is not a string is refused with 400, and a parent
on a board the caller cannot see is still refused and recorded under
ParentBleed. `tests/restCardParent.test.cjs` and
`tests/playwright/specs/rest-card-parent.e2e.js` cover a stored parent, the
subtask it renders as, an empty parent and the refused requests.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/1418cb8480e0ca13ccecc54290b16c36d40f82a6">An integration update with a refused URL changes nothing</a>. Thanks to AhmedLukman and xet7.</summary>
`PUT /api/boards/:boardId/integrations/:intId` wrote `enabled` and `title`
before it checked the new URL against the SSRF rules (GHSA-hc3x-hq3m-663q), so a
request whose URL was refused with 400 had already changed those two fields. The
URL is validated first now, like the delivery settings, and a refused request
leaves the integration as it was. `tests/restIntegrationUpdate.test.cjs` and its
Playwright spec pin the order.
</details>
and has the following developer-tooling fixes:
**Release builds** - the single-file executables.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/c35c672ffb398b68be22f257087db28738eb4701">The 32-bit host Node.js of a single file is its bundle's exact version</a>. Thanks to xet7.</summary>
The v13.07 single files for armhf, armv6 and armv7 stopped on "The bundle's
Node.js is v26.13.0 but this is v26.13.1". A 32-bit target's SEA blob is
written by a 32-bit Node.js, and `.github/workflows/single-file.yml` borrowed
the i386 bundle's. Each bundle takes the newest Node.js of the pinned major its
platform has, so i386 had v26.13.1 while 32-bit ARM had v26.13.0. The host is
now resolved with `releases/resolve-node-source.sh` at the target bundle's exact
version, checked against its published SHA256, and refused unless it reports
that version. `tests/singleFile.test.cjs` pins all three, and that the host is
never taken from another platform's bundle.
</details>
**Browser tests** - what a spec may rely on from the database.
- [list-sync-estimate's checkbox test no longer depends on the order an index returns](https://github.com/wekan/wekan/commit/af76406d127568b45b0e76659160a8821cdf00a2) -
it expected an unsorted find of activities in insertion order, which
activities' cardId/createdAt index returns newest first. Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
# v13.07 2026-11-12 WeKan ® release
**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.
This release fixes the following CRITICAL SECURITY ISSUE of [ListLockAttachBleed](https://wekan.fi/hall-of-fame/listlockattachbleed/):
<details>
<summary><a href="https://github.com/wekan/wekan/commit/7bb3e13ba9">A list that refuses a role write access refuses its attachment API writes too</a>. Thanks to Furkan Derse and xet7.</summary>
[ListLockAttachBleed](https://wekan.fi/hall-of-fame/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](https://wekan.fi/hall-of-fame/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.
</details>
and fixes the following SECURITY ISSUES found by GitHub CodeQL code scanning:
<details>
<summary><a href="https://github.com/wekan/wekan/commit/2b65b713a0f7b537efbe7c25bb2a8b454e88d1ad">Alerts #602 and #603: no test hands a path to a shell at all</a>. Thanks to GitHub CodeQL and xet7.</summary>
The fix for #601 passed the paths to `bash -c` as arguments rather than
pasting them into the script, but that still hands a temporary path to a
shell, and CodeQL flagged the two umask tests in
`tests/releaseDownloads.test.cjs` again. They no longer use a shell: `fetch.sh`
runs as bash's program with its arguments, the umask is set on the test's
process and put back, and `chmod +x` is `fs.chmodSync`. The macOS sandbox test
runs its probes as programs the same way. The guard now refuses any value
given to a shell's `-c` script as an argument, and found one more test doing
it. The findings were in tests, not in WeKan, so there is no attempt to show in
Admin Panel → Problems.
</details>
and adds the following new features:
**The Admin Panel** - Problems, and getting rid of the ones that are handled.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/fefabbf113">Problems has a Clear button, and resolved problems age out on their own</a>. Thanks to Raymond-Voogt and xet7.</summary>
The problem streams were append-only, and Acknowledge only reset the "new"
count, so a problem fixed long ago stayed in the table and buried the ones
that are live now. Clear, beside Acknowledge, calls the admin-only
`clearEventLog`, which deletes the checked streams' events up to now and
stamps the acknowledgement. Anything that happens after the click shows as a
new problem again, and an unknown stream in the list clears nothing. A daily
sweep, claimed once per installation, deletes events older than
`EVENTLOG_RETENTION_DAYS` (default 90, `0` keeps them forever); a recurring
problem's folded row keeps a recent date, so it stays. The setting is listed
on every platform and in the Helm chart, and the button is translated to
every language. `tests/eventLogClearAndRetention.test.cjs` runs Clear and the
sweep on an in-memory log, including a non-admin and an unknown stream, and
`tests/playwright/specs/problems-clear.e2e.js` clears one stream in the UI.
</details>
and updates the following dependencies:
- [**fast-xml-parser 5.11.2 → 5.12.0**](https://github.com/wekan/wekan/commit/a76a19058ac896651ccd30311c36d48ee7f47b86) — Dependabot
alert #188: with `stopNodes`, an unterminated stop node made it rescan the
rest of the input from every `<`, O(n²) CPU; 5.12.0 stops at the first
failed scan. Brought in by the Azure and Google Cloud storage clients. The
test runs the alert's input and pins that no lockfile resolves an older
version. Thanks to dependabot.
and fixes the following bugs:
**Cards** - how spent time is shown.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/3e8e8039ff">Spent time is shown as a duration, not decimal hours</a>. Thanks to brlin-tw and xet7.</summary>
A card's spent time showed as decimal hours, such as 12.58 for 12 hours and
35 minutes, which reads as twelve hours and fifty-eight minutes. The badge now
shows `12h35m`, drops the units that are zero and shows `0s` for none, and its
tooltip keeps the rounded hours. The formatter is
`models/lib/spentTimeFormat.js`; `tests/spentTimeFormat.test.cjs` pins it and
`tests/playwright/specs/spent-time-format.e2e.js` checks the badge. A
follow-up imports it the way `cardTime.js` imports its other helpers.
</details>
**The REST API** - logging out a token.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/fd59a8ff70">POST /api/deletetoken waits for the token to be deleted before answering</a>. Thanks to AhmedLukman and xet7.</summary>
`Accounts.destroyToken` was not awaited, so the route answered success before
the token was gone, and a failed database write never reached its error
handler. It is awaited now. `tests/restTokenRevocation.test.cjs` covers a slow
and a failed deletion, authorization and session isolation, and
`tests/playwright/specs/rest-token-revocation.e2e.js` logs a browser out with
it.
</details>
**Database indexes** - the queries that scanned whole collections.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/8dc77a89d8">Indexes for the LDAP id, cards' assignees and members, and History by entity and hash</a>. Thanks to Raymond-Voogt and xet7.</summary>
An LDAP login looked the user up by `services.ldap.id`, a member's cards were
found by `assignees` and `members`, and the card history by entity and by
integrity hash, all without an index, so each scanned its whole collection on
a large installation. They have indexes now, the LDAP one sparse.
`tests/cardQueryIndexes.test.cjs` and `tests/ldapAndHistoryIndexes.test.cjs`
pin them.
</details>
and adds the following developer tool:
<details>
<summary><a href="https://github.com/wekan/wekan/commit/801f8956fe813a5da0264abf660c18363d2d3bc2">releases/sec downloads a GitHub organization's Security and quality alerts with gh</a>. Thanks to xet7.</summary>
`releases/sec/download-github-security.sh wekan` saves every repository's
Dependabot, code scanning, secret scanning and security advisory alerts to
`.tools/log/sec/<organization>/<repository>/<YYYY-MM-DD_HH-MM-SS>/`, a
directory per kind with a file per alert and a `SUMMARY.md` of the open ones.
It runs the GitHub CLI outside the editor's sandbox, where `gh` and its login
are, so the alerts can be read and fixed from the files inside it. A kind
GitHub does not answer is recorded with its reason, a secret scanning alert's
secret is redacted unless asked for, and a name that is not a GitHub name is
refused before it becomes a path. The test runs it against a stand-in `gh`;
see `releases/sec/README.md`.
</details>
Thanks to above GitHub users for their contributions and translators for their translations.
# v13.06 2026-11-11 WeKan ® release
**In short:** **CodeQL** alert #601 in a test is fixed, with two more tests
+28 -24
View File
@@ -5,6 +5,34 @@ each one changed and the project status are in
Written by `node releases/changelog-short.mjs` from CHANGELOG-big.md:
make changes there.
# v13.09 2026-11-12 WeKan ® release
The release's **Snap Store** credential check retries installing
snapcraft, so one Snap Store timeout no longer stops a release.
[All changes in v13.09](CHANGELOG-big.md#v1309-2026-11-12-wekan--release)
# v13.08 2026-11-12 WeKan ® release
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.
[All changes in v13.08](CHANGELOG-big.md#v1308-2026-11-12-wekan--release)
# v13.07 2026-11-12 WeKan ® release
**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.
[All changes in v13.07](CHANGELOG-big.md#v1307-2026-11-12-wekan--release)
# v13.06 2026-11-11 WeKan ® release
**CodeQL** alert #601 in a test is fixed, with two more tests
@@ -24,27 +52,3 @@ Productivity** export no longer fails for a board with a card whose list is
archived.
[All changes in v13.05](CHANGELOG-big.md#v1305-2026-11-10-wekan--release)
# v13.04 2026-11-09 WeKan ® release
**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.
[All changes in v13.04](CHANGELOG-big.md#v1304-2026-11-09-wekan--release)
# v13.03 2026-11-09 WeKan ® release
The amd64 **snaps** no longer fail the release when the Ubuntu
archive is briefly unreachable: the build waits for it and retries once.
[All changes in v13.03](CHANGELOG-big.md#v1303-2026-11-09-wekan--release)
# v13.02 2026-11-09 WeKan ® release
**UnassignedArchiveBleed** is fixed: a member with the
**Normal, assigned only** role archives and converts only the cards assigned
to them, through every card method.
[All changes in v13.02](CHANGELOG-big.md#v1302-2026-11-09-wekan--release)
+3 -2
View File
@@ -38,7 +38,7 @@ FROM --platform=$BUILDPLATFORM debian:trixie AS bundle
ARG TARGETARCH
ARG TARGETVARIANT
ARG VERSION=13.06
ARG VERSION=13.09
ARG DEBIAN_FRONTEND=noninteractive
COPY --chmod=755 releases/check-telemetry.py /tmp/check-telemetry.py
@@ -148,7 +148,7 @@ ARG DEBIAN_FRONTEND=noninteractive
ENV \
DEBUG=false \
DDP_TRANSPORT=sockjs \
NODE_VERSION=v26.13.0 \
NODE_VERSION=v26.13.1 \
METEOR_RELEASE=METEOR@3.6 \
USE_EDGE=false \
NPM_VERSION=12.2.2 \
@@ -318,6 +318,7 @@ ENV \
WEKAN_DISK_WATCH_PATHS="" \
WEKAN_RAM_MONITOR="" \
WEKAN_IMPORT_RUN_STALE_MS="" \
EVENTLOG_RETENTION_DAYS="" \
CORS="" \
CORS_ALLOW_HEADERS="" \
CORS_EXPOSE_HEADERS="" \
+1 -1
View File
@@ -1,5 +1,5 @@
appId: wekan-public/apps/77b94f60-dec9-0136-304e-16ff53095928
appVersion: "v13.06.0"
appVersion: "v13.09.0"
files:
userUploads:
- README.md
Executable
+3
View File
@@ -0,0 +1,3 @@
#!/bin/bash
export PACKAGE_DIRS="$(pwd)/packages"
+5 -3
View File
@@ -2,6 +2,8 @@ import { TAPi18n } from '/imports/i18n';
import Cards from '/models/cards';
import { getCurrentCardIdFromContext } from '/client/lib/currentCard';
import { backIfOwnPopup } from '/client/lib/popupBack';
// #6890: the badge shows a duration, the tooltip hours to two decimals.
import { formatSpentTime, roundedSpentHours } from '/models/lib/spentTimeFormat';
function getCardId() {
return getCurrentCardIdFromContext();
@@ -63,17 +65,17 @@ Template.cardSpentTime.helpers({
if (card.getIsOvertime && card.getIsOvertime()) {
return `${TAPi18n.__(
'overtime',
)} ${card.getSpentTime()} ${TAPi18n.__('hours')}`;
)} ${roundedSpentHours(card.getSpentTime())} ${TAPi18n.__('hours')}`;
} else if (card.getSpentTime) {
return `${TAPi18n.__(
'card-spent',
)} ${card.getSpentTime()} ${TAPi18n.__('hours')}`;
)} ${roundedSpentHours(card.getSpentTime())} ${TAPi18n.__('hours')}`;
}
return '';
},
showTime() {
const card = Cards.findOne(this._id) || this;
return card.getSpentTime ? card.getSpentTime() : '';
return card.getSpentTime ? formatSpentTime(card.getSpentTime()) : '';
},
getIsOvertime() {
const card = Cards.findOne(this._id) || this;
@@ -1,3 +0,0 @@
.minicard-title .minicard-complete-toggle {
display: none;
}
@@ -100,5 +100,6 @@ template(name="problemsSummary")
span.admin-problem-count {{area.count}} {{_ 'new-problems'}}
.admin-problem-actions
button.js-ack-checked.primary {{_ 'acknowledge'}}
button.js-clear-checked {{_ 'clear-problems'}}
else
p {{_ 'no-new-problems'}}
@@ -232,4 +232,14 @@ Template.problemsSummary.events({
if (!streams.length) return;
Meteor.call('acknowledgeEventLog', streams, () => templateInstance.reload());
},
// Clear (#6893) removes the checked streams' events up to now, so a resolved
// problem stops showing, where Acknowledge only resets the count.
'click .js-clear-checked'(event, templateInstance) {
const streams = Array.from(templateInstance.findAll('.js-problem-check:checked'))
.map(el => el.getAttribute('data-stream'))
.filter(Boolean);
if (!streams.length) return;
Meteor.call('clearEventLog', streams, () => templateInstance.reload());
},
});
-1
View File
@@ -54,5 +54,4 @@ import '/client/components/cards/subtasks.css';
import '/client/components/cards/similarCards.css';
import '/client/components/cards/fromText.css';
import '/client/components/cards/whiteboard.css';
import '/client/components/cards/minicardOverrides.css';
+4
View File
@@ -986,6 +986,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
+4
View File
@@ -988,6 +988,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
@@ -975,6 +975,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
+4
View File
@@ -992,6 +992,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
@@ -898,6 +898,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
+4
View File
@@ -1129,6 +1129,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
+4
View File
@@ -973,6 +973,10 @@ services:
# progress counts as interrupted and can be resumed or discarded (at least
# 60000).
#- WEKAN_IMPORT_RUN_STALE_MS=600000
# EVENTLOG_RETENTION_DAYS : Days after which an Admin Panel / Problems event
# is deleted by the daily sweep, so resolved problems age out; a recurring
# problem keeps a recent date and stays. Default 90, 0 = keep forever.
#- EVENTLOG_RETENTION_DAYS=90
#---------------------------------------------------------------
# ATTACHMENT RETENTION (models/lib/attachmentRetention.js). Off unless set.
# ATTACHMENTS_RETENTION_DAYS : once a night, delete card attachments older
@@ -0,0 +1,14 @@
# WeKan settings. Every setting is listed, with comments, in
# https://github.com/wekan/wekan/blob/main/docker-compose.yml
# Restart after editing: systemctl restart wekan
# The address users open WeKan at. WeKan builds its links from it and its
# live updates connect to it, so it must match the address in the browser.
ROOT_URL=http://localhost:8080
PORT=8080
# Database, attachments and avatars: /var/lib/wekan/files/{db,attachments,avatars}
WRITABLE_PATH=/var/lib/wekan
#MAIL_URL=smtp://user:password@mailserver.example.com:25/
#MAIL_FROM=WeKan <wekan@example.com>
@@ -10,7 +10,7 @@ This is without container (without Docker or Snap).
Right click and download files 1-4:
1. [wekan-13.06-win64.zip](https://github.com/wekan/wekan/releases/download/v13.06/wekan-13.06-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
1. [wekan-13.09-win64.zip](https://github.com/wekan/wekan/releases/download/v13.09/wekan-13.09-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
2. [node.exe](https://nodejs.org/dist/latest-v26.x/win-x64/node.exe)
@@ -22,7 +22,7 @@ Right click and download files 1-4:
6. Double click `mongodb-windows-x86_64-7.0.34-signed.msi` . In installer, uncheck downloading MongoDB compass.
7. Unzip `wekan-13.06-win64.zip` , inside it is directory `bundle`, to it copy other files:
7. Unzip `wekan-13.09-win64.zip` , inside it is directory `bundle`, to it copy other files:
```
bundle (directory)
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Peukara pangkalan data",
"new-problems": "peukara barô",
"acknowledge": "Teurimong",
"clear-problems": "Peugléh",
"rulesReportTitle": "Laporan Atôran",
"boardsReportTitle": "Laporan Papan",
"cardsReportTitle": "Laporan Kad",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Databasisprobleme",
"new-problems": "nuwe probleme",
"acknowledge": "Erken",
"clear-problems": "Maak skoon",
"rulesReportTitle": "Reëlsverslag",
"boardsReportTitle": "Raadsverslag",
"cardsReportTitle": "Kaarte Verslag",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Databasisprobleme",
"new-problems": "nuwe probleme",
"acknowledge": "Erken",
"clear-problems": "Maak skoon",
"rulesReportTitle": "Reëlsverslag",
"boardsReportTitle": "Raadsverslag",
"cardsReportTitle": "Kaarte Verslag",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Nsɛm akorabea mu haw",
"new-problems": "Fa ade foforo ka ho",
"acknowledge": "Gye tom",
"clear-problems": "Pepa",
"rulesReportTitle": "Mmara ho amanneɛbɔ",
"boardsReportTitle": "Bɔɔd ho amanneɛbɔ",
"cardsReportTitle": "Kaad ho amanneɛbɔ",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "የውሂብ ጎታ ችግሮች",
"new-problems": "አዲስ ችግሮች",
"acknowledge": "እውቅና ስጥ",
"clear-problems": "አጽዳ",
"rulesReportTitle": "የደንቦች ሪፖርት",
"boardsReportTitle": "የሰሌዳዎች ሪፖርት",
"cardsReportTitle": "የካርዶች ሪፖርት",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas d’a base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Limpiar",
"rulesReportTitle": "Informe sobre as Reglas",
"boardsReportTitle": "Informe sobre os Tableros",
"cardsReportTitle": "Informe sobre as Tarchetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "مشاكل قاعدة البيانات",
"new-problems": "مشاكل جديدة",
"acknowledge": "إقرار",
"clear-problems": "مسح",
"rulesReportTitle": "تقرير القواعد",
"boardsReportTitle": "تقرير اللوحات",
"cardsReportTitle": "تقرير البطاقات",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "مشاكل قاعدة البيانات",
"new-problems": "مشاكل جديدة",
"acknowledge": "إقرار",
"clear-problems": "مسح",
"rulesReportTitle": "تقرير القواعد",
"boardsReportTitle": "تقرير اللوحات",
"cardsReportTitle": "تقرير البطاقات",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "مشاكل قاعدة البيانات",
"new-problems": "مشاكل جديدة",
"acknowledge": "إقرار",
"clear-problems": "مسح",
"rulesReportTitle": "تقرير القواعد",
"boardsReportTitle": "تقرير اللوحات",
"cardsReportTitle": "تقرير البطاقات",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "مشاكل قاعدة البيانات",
"new-problems": "مشاكل جداد",
"acknowledge": "تأكيد",
"clear-problems": "مسح",
"rulesReportTitle": "تقرير القواعد",
"boardsReportTitle": "تقرير اللوحات",
"cardsReportTitle": "تقرير البطاقات",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "ডাটাবেছৰ সমস্যাসমূহ",
"new-problems": "নতুন সমস্যাসমূহ",
"acknowledge": "স্বীকাৰ কৰক",
"clear-problems": "পৰিষ্কাৰ কৰক",
"rulesReportTitle": "নিয়মৰ প্ৰতিবেদন",
"boardsReportTitle": "বৰ্ডৰ প্ৰতিবেদন",
"cardsReportTitle": "কাৰ্ডৰ প্ৰতিবেদন",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemes de la base de datos",
"new-problems": "problemes nuevos",
"acknowledge": "Reconocer",
"clear-problems": "Llimpiar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe de los tableros",
"cardsReportTitle": "Informe de les tarxetes",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Aymar aruna: Database problems",
"new-problems": "machaqa problems",
"acknowledge": "Aymar aruna: Acknowledge",
"clear-problems": "Q'umachaña",
"rulesReportTitle": "Rules yatiyawi",
"boardsReportTitle": "pirqanaka yatiyawi",
"cardsReportTitle": "tarjetanaka yatiyawi",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Verilənlər bazası problemləri",
"new-problems": "yeni problem",
"acknowledge": "Təsdiqlə",
"clear-problems": "Təmizlə",
"rulesReportTitle": "Qaydalar Hesabatı",
"boardsReportTitle": "İdarə Heyətinin Hesabatı",
"cardsReportTitle": "Kartlar Hesabatı",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Verilənlər bazası problemləri",
"new-problems": "yeni problem",
"acknowledge": "Təsdiqlə",
"clear-problems": "Təmizlə",
"rulesReportTitle": "Qaydalar Hesabatı",
"boardsReportTitle": "İdarə Heyətinin Hesabatı",
"cardsReportTitle": "Kartlar Hesabatı",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Verilənlər bazası problemləri",
"new-problems": "yeni problem",
"acknowledge": "Təsdiqlə",
"clear-problems": "Təmizlə",
"rulesReportTitle": "Qaydalar Hesabatı",
"boardsReportTitle": "İdarə Heyətinin Hesabatı",
"cardsReportTitle": "Kartlar Hesabatı",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Мәғлүмәттәр базаһы мәсьәләләре",
"new-problems": "яңы мәсьәләләр",
"acknowledge": "Таныу",
"clear-problems": "Таҙартырға",
"rulesReportTitle": "Ҡағиҙәләр хисабы",
"boardsReportTitle": "Таҡталар хисабы",
"cardsReportTitle": "Карточкалар хисабы",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Праблемы базы даных",
"new-problems": "новых праблем",
"acknowledge": "Пацвердзіць",
"clear-problems": "Ачысціць",
"rulesReportTitle": "Справаздача па правілах",
"boardsReportTitle": "Справаздача па дошках",
"cardsReportTitle": "Справаздача па картках",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Проблеми с базата данни",
"new-problems": "нови проблема",
"acknowledge": "Потвърждаване",
"clear-problems": "Изчистване",
"rulesReportTitle": "Отчет за правилата",
"boardsReportTitle": "Отчет за таблата",
"cardsReportTitle": "Отчет за картите",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "डेटाबेस समस्या",
"new-problems": "नया समस्या",
"acknowledge": "जानकारी स्वीकार करीं",
"clear-problems": "साफ करीं",
"rulesReportTitle": "नियम रपट",
"boardsReportTitle": "बोर्ड रपट",
"cardsReportTitle": "कार्ड रपट",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Ol problem blong databes",
"new-problems": "niu problem",
"acknowledge": "Talem se yu kasem",
"clear-problems": "Klinim",
"rulesReportTitle": "Ripot blong ol rul",
"boardsReportTitle": "Ripot blong Ol bod",
"cardsReportTitle": "Ripot blong Ol kad",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datakurun gɛlɛyaw",
"new-problems": "gɛlɛya kuraw",
"acknowledge": "A sɔrɔ",
"clear-problems": "Saniya",
"rulesReportTitle": "Sariyaw lapɔrɔ",
"boardsReportTitle": "Tabaliw lapɔrɔ",
"cardsReportTitle": "Karataw lapɔrɔ",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "ডেটাবেসের সমস্যা",
"new-problems": "নতুন সমস্যা",
"acknowledge": "স্বীকার করুন",
"clear-problems": "মুছুন",
"rulesReportTitle": "নিয়মের প্রতিবেদন",
"boardsReportTitle": "বোর্ডের প্রতিবেদন",
"cardsReportTitle": "কার্ডের প্রতিবেদন",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "གཞི་གྲངས་མཛོད་ཀྱི་གནད་དོན།",
"new-problems": "གནད་དོན་གསར་པ།",
"acknowledge": "ངོས་ལེན།",
"clear-problems": "གཙང་སེལ།",
"rulesReportTitle": "སྒྲིག་སྲོལ་སྙན་ཞུ།",
"boardsReportTitle": "ལས་སྟེགས་སྙན་ཞུ།",
"cardsReportTitle": "བྱང་བུའི་སྙན་ཞུ།",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Kudennoù an diaz roadennoù",
"new-problems": "kudenn nevez",
"acknowledge": "Anzav",
"clear-problems": "Skarzhañ",
"rulesReportTitle": "Raport a benn ar merde",
"boardsReportTitle": "Raport a benn taolennnoù",
"cardsReportTitle": "Raport a benn kartennnoù",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemi baze podataka",
"new-problems": "novih problema",
"acknowledge": "Potvrdi",
"clear-problems": "Očisti",
"rulesReportTitle": "Izvještaj o pravilima",
"boardsReportTitle": "Izvještaj o tablama",
"cardsReportTitle": "Izvještaj o karticama",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Үгэгдэлэй сангай асуудалнууд",
"new-problems": "шэнэ асуудалнууд",
"acknowledge": "Мэдэрхэ",
"clear-problems": "Арилгаха",
"rulesReportTitle": "Дүримүүдэй тайлан",
"boardsReportTitle": "Самбарнуудай тайлан",
"cardsReportTitle": "Картануудай тайлан",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemes de la base de dades",
"new-problems": "problemes nous",
"acknowledge": "Reconeix",
"clear-problems": "Neteja",
"rulesReportTitle": "Informe de normes",
"boardsReportTitle": "Informe de les Juntes",
"cardsReportTitle": "Informe de fitxes",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemes de la base de dades",
"new-problems": "problemes nous",
"acknowledge": "Reconeix",
"clear-problems": "Neteja",
"rulesReportTitle": "Informe de normes",
"boardsReportTitle": "Informe de les Juntes",
"cardsReportTitle": "Informe de fitxes",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemes de la base de dades",
"new-problems": "problemes nous",
"acknowledge": "Reconeix",
"clear-problems": "Neteja",
"rulesReportTitle": "Informe de normes",
"boardsReportTitle": "Informe de les Juntes",
"cardsReportTitle": "Informe de fitxes",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "ᎧᏃᎮᏓ ᏗᎦᏓᎭ",
"new-problems": "ᎢᏤ ᏗᎦᏓᎭ",
"acknowledge": "ᎠᏓᏂᎸᏤᏗ",
"clear-problems": "ᎯᏅᎦᎸ",
"rulesReportTitle": "ᏗᎧᎿᏩᏛᏍᏗ ᎧᏃᎮᏓ",
"boardsReportTitle": "ᏗᎦᏍᎩᎸ ᎧᏃᎮᏓ",
"cardsReportTitle": "ᏗᎪᏪᎵ ᏗᏍᏗ ᎧᏃᎮᏓ",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "کێشەکانی بنکەدراوە",
"new-problems": "کێشە نوێکان",
"acknowledge": "پەسەند بکە",
"clear-problems": "پاککردنەوە",
"rulesReportTitle": "ڕاپۆرتی یاساکان",
"boardsReportTitle": "ڕاپۆرتی تەختەکان",
"cardsReportTitle": "ڕاپۆرتی کارتەکان",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "数据库问题",
"new-problems": "个新问题",
"acknowledge": "确认",
"clear-problems": "清除",
"rulesReportTitle": "规则报告",
"boardsReportTitle": "看板报告",
"cardsReportTitle": "卡片报告",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Prublemi di a basa di dati",
"new-problems": "prublemi novi",
"acknowledge": "Cunfirmà",
"clear-problems": "Sguassà",
"rulesReportTitle": "Raportu di e regule",
"boardsReportTitle": "Raportu di e tavule",
"cardsReportTitle": "Raportu di e carte",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problémy databáze",
"new-problems": "nových problémů",
"acknowledge": "Potvrdit",
"clear-problems": "Vymazat",
"rulesReportTitle": "Report pravidel",
"boardsReportTitle": "Report tabel",
"cardsReportTitle": "Report karet",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problémy databáze",
"new-problems": "nových problémů",
"acknowledge": "Potvrdit",
"clear-problems": "Vymazat",
"rulesReportTitle": "Report pravidel",
"boardsReportTitle": "Report tabel",
"cardsReportTitle": "Report karet",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemë bazë dónëch",
"new-problems": "nowych problemòw",
"acknowledge": "Pòcwierdzë",
"clear-problems": "Wëczëszczë",
"rulesReportTitle": "Rapòrt reglów",
"boardsReportTitle": "Raport tôblëcòw",
"cardsReportTitle": "Raport kôrtòw",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Палӑрту базин проблемӗсем",
"new-problems": "ҫӗнӗ проблемӑсем",
"acknowledge": "Йышӑнас",
"clear-problems": "Тасатас",
"rulesReportTitle": "Правилӑсен отчӗчӗ",
"boardsReportTitle": "Хӑмасен отчӗчӗ",
"cardsReportTitle": "Карточкӑсен отчӗчӗ",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemau cronfa ddata",
"new-problems": "problemau newydd",
"acknowledge": "Cydnabod",
"clear-problems": "Clirio",
"rulesReportTitle": "Adroddiad Rheolau",
"boardsReportTitle": "Adroddiad y Byrddau",
"cardsReportTitle": "Adroddiad Cardiau",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemau cronfa ddata",
"new-problems": "problemau newydd",
"acknowledge": "Cydnabod",
"clear-problems": "Clirio",
"rulesReportTitle": "Adroddiad Rheolau",
"boardsReportTitle": "Adroddiad y Byrddau",
"cardsReportTitle": "Adroddiad Cardiau",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Databaseproblemer",
"new-problems": "nye problemer",
"acknowledge": "Bekræft",
"clear-problems": "Nulstil",
"rulesReportTitle": "Regelrapport",
"boardsReportTitle": "Tavlerapport",
"cardsReportTitle": "Kortrapport",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datenbankprobleme",
"new-problems": "neue Probleme",
"acknowledge": "Bestätigen",
"clear-problems": "Zurücksetzen",
"rulesReportTitle": "Regeln-Bericht",
"boardsReportTitle": "Board-Bericht",
"cardsReportTitle": "Karten-Bericht",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datenbankprobleme",
"new-problems": "neue Probleme",
"acknowledge": "Bestätigen",
"clear-problems": "Zurücksetzen",
"rulesReportTitle": "Regeln-Bericht",
"boardsReportTitle": "Board-Bericht",
"cardsReportTitle": "Karten-Bericht",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datenbankprobleme",
"new-problems": "neue Probleme",
"acknowledge": "Bestätigen",
"clear-problems": "Zurücksetzen",
"rulesReportTitle": "Regeln-Bericht",
"boardsReportTitle": "Boardbericht",
"cardsReportTitle": "Kartenbericht",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datenbankprobleme",
"new-problems": "neue Probleme",
"acknowledge": "Bestätigen",
"clear-problems": "Zurücksetzen",
"rulesReportTitle": "Regeln-Bericht",
"boardsReportTitle": "Boardbericht",
"cardsReportTitle": "Kartenbericht",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "གཞི་གྲངས་མཛོད་གནད་དོན།",
"new-problems": "གནད་དོན་གསར་པ།",
"acknowledge": "ངོས་ལེན།",
"clear-problems": "བསལ།",
"rulesReportTitle": "སྒྲིག་ལམ་སྙན་ཞུ།",
"boardsReportTitle": "བྱང་གཞིའི་སྙན་ཞུ།",
"cardsReportTitle": "ཤོག་བྱང་སྙན་ཞུ།",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Nyatakakadzraɖoƒe ƒe kuxiwo",
"new-problems": "kuxi yeyewo",
"acknowledge": "Lɔ̃ ɖe edzi",
"clear-problems": "Tutui ɖa",
"rulesReportTitle": "Sewo ƒe nyatakakagbalẽ",
"boardsReportTitle": "Kpekpeɖeŋuwo ƒe nyatakakagbalẽ",
"cardsReportTitle": "Kaɖiwo ƒe nyatakakagbalẽ",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Προβλήματα βάσης δεδομένων",
"new-problems": "νέα προβλήματα",
"acknowledge": "Επιβεβαίωση",
"clear-problems": "Εκκαθάριση",
"rulesReportTitle": "Αναφορά κανόνων",
"boardsReportTitle": "Αναφορά πινάκων",
"cardsReportTitle": "Αναφορά καρτών",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Προβλήματα βάσης δεδομένων",
"new-problems": "νέα προβλήματα",
"acknowledge": "Επιβεβαίωση",
"clear-problems": "Εκκαθάριση",
"rulesReportTitle": "Αναφορά κανόνων",
"boardsReportTitle": "Αναφορά πινάκων",
"cardsReportTitle": "Αναφορά καρτών",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Database problems",
"new-problems": "new problems",
"acknowledge": "Acknowledge",
"clear-problems": "Clear",
"rulesReportTitle": "Rules Report",
"boardsReportTitle": "Boards Report",
"cardsReportTitle": "Cards Report",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datumbazaj problemoj",
"new-problems": "novaj problemoj",
"acknowledge": "Konfirmi",
"clear-problems": "Viŝi",
"rulesReportTitle": "Raporto pri reguloj",
"boardsReportTitle": "Raporto pri tabuloj",
"cardsReportTitle": "Raporto pri kartoj",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Problemas de la base de datos",
"new-problems": "problemas nuevos",
"acknowledge": "Confirmar",
"clear-problems": "Borrar",
"rulesReportTitle": "Informe sobre las Reglas",
"boardsReportTitle": "Informe sobre los Tableros",
"cardsReportTitle": "Informe sobre las Tarjetas",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Andmebaasi probleemid",
"new-problems": "uut probleemi",
"acknowledge": "Kinnita",
"clear-problems": "Tühjenda",
"rulesReportTitle": "Reeglite aruanne",
"boardsReportTitle": "Juhatuse aruanne",
"cardsReportTitle": "Kaartide aruanne",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Datu-basearen arazoak",
"new-problems": "arazo berri",
"acknowledge": "Berretsi",
"clear-problems": "Garbitu",
"rulesReportTitle": "Arauen txostena",
"boardsReportTitle": "Arbelen txostena",
"cardsReportTitle": "Txartelen txostena",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "مشکلات پایگاه داده",
"new-problems": "مشکل جدید",
"acknowledge": "تأیید",
"clear-problems": "پاک کردن",
"rulesReportTitle": "گزارش قوانین",
"boardsReportTitle": "گزارش بردها",
"cardsReportTitle": "گزارش کارت‌ها",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "مشکلات پایگاه داده",
"new-problems": "مشکل جدید",
"acknowledge": "تأیید",
"clear-problems": "پاک کردن",
"rulesReportTitle": "گزارش قوانین",
"boardsReportTitle": "گزارش بردها",
"cardsReportTitle": "گزارش کارت‌ها",
+1
View File
@@ -2380,6 +2380,7 @@
"databaseReportTitle": "Caɗeele ruttorde keɓe",
"new-problems": "caɗeele kese",
"acknowledge": "Jaɓ",
"clear-problems": "Laɓɓin",
"rulesReportTitle": "Jaŋtol kuule",
"boardsReportTitle": "Jaŋtol alluuje",
"cardsReportTitle": "Jaŋtol karte",
Loaded 100 of 338 files, more files were not shown because too many files have changed in this diff. Show more