mirror of
https://github.com/wekan/wekan.git
synced 2026-11-18 05:45:02 -05:00
Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
b988efae19 | ||
|
|
8a8f036947 | ||
|
|
1e5ae8f649 | ||
|
|
40c3ee098e | ||
|
|
7441937f67 | ||
|
|
0ea935e5d9 | ||
|
|
8dbabc145f | ||
|
|
e057e9454e | ||
|
|
b30f4967cb |
No files matched your search
@@ -710,10 +710,49 @@ jobs:
|
||||
fi
|
||||
done
|
||||
|
||||
- name: Verify the release bundle reports the release version
|
||||
# Belt-and-suspenders against the "image tagged vX shows vY in the Admin
|
||||
# Panel" bug: the image is just the unzipped wekan-<version>-<arch>.zip
|
||||
# bundle (Dockerfile moves it to /build), and the Admin Panel shows that
|
||||
# bundle's app package.json version (server/statistics.js reads
|
||||
# require('/package.json').version). Assert the amd64 bundle's WeKan
|
||||
# version equals the release version BEFORE the expensive multi-arch
|
||||
# buildx, so a stale/mismatched bundle fails fast with a clear message
|
||||
# instead of shipping (and pushing to three registries) a mislabeled image.
|
||||
run: |
|
||||
set -euo pipefail
|
||||
url="https://github.com/wekan/wekan/releases/download/v${VERSION}/wekan-${VERSION}-amd64.zip"
|
||||
wget -q "$url" -O bundle.zip
|
||||
tmp="$(mktemp -d)"
|
||||
# Extract only package.json files (not the whole multi-hundred-MB bundle).
|
||||
unzip -o -q bundle.zip '*package.json' -d "$tmp"
|
||||
# The WeKan app package.json is the only one whose "version" carries a
|
||||
# leading 'v' (e.g. "v9.61.0"); every dependency uses plain semver. So a
|
||||
# v-prefixed "version" uniquely identifies the app's own package.json.
|
||||
found="$(grep -rhoE '"version": "v[0-9][^"]*"' "$tmp" \
|
||||
| grep -oE 'v[0-9][^"]*' | sort -u | head -1 || true)"
|
||||
rm -rf "$tmp" bundle.zip
|
||||
if [ -z "$found" ]; then
|
||||
echo "::error::Could not find a v-prefixed WeKan version in the bundle's package.json files."
|
||||
exit 1
|
||||
fi
|
||||
if [ "$found" != "v${VERSION}.0" ] && [ "$found" != "v${VERSION}" ]; then
|
||||
echo "::error::Bundle reports app version $found but the release is v${VERSION}. The bundle baked into the image is stale/mismatched — the Admin Panel would show $found. Aborting before build."
|
||||
exit 1
|
||||
fi
|
||||
echo "Bundle app version $found matches release v${VERSION}."
|
||||
|
||||
- name: Build and push multi-arch image
|
||||
# Pass VERSION explicitly as a build-arg. The Dockerfile's `ARG VERSION`
|
||||
# default is only a fallback for manual builds; the release version is the
|
||||
# authoritative source here. Without this the image would build against the
|
||||
# Dockerfile default (downloading that version's wekan-<v>-<arch>.zip and
|
||||
# baking its package.json), so a v${VERSION}-tagged image could ship — and
|
||||
# report in the Admin Panel — a stale, different version.
|
||||
run: |
|
||||
docker buildx build \
|
||||
--platform linux/amd64,linux/arm64 \
|
||||
--build-arg VERSION=${VERSION} \
|
||||
-t wekanteam/wekan:v${VERSION} \
|
||||
-t wekanteam/wekan:latest \
|
||||
-t quay.io/wekan/wekan:v${VERSION} \
|
||||
|
||||
@@ -26,6 +26,61 @@ Versions:
|
||||
- WeKan 8.00-8.06 had wrong raw database directory setting /var/snap/wekan/common/wekan and some cards were not visible,
|
||||
it was fixed at WeKan 8.07 where database directory is back to /var/snap/wekan/common and all cards are visible.
|
||||
|
||||
# v9.63 2026-06-19 WeKan ® release
|
||||
|
||||
This release adds the following features:
|
||||
|
||||
- [Fix the wekan.fi install page version never updating from a stale value](https://github.com/wekan/wekan/commit/40c3ee098).
|
||||
The `release-all.yml` website job ran every release but the install page's
|
||||
version stayed frozen at v9.57: `releases/release-website.sh` updated it with a
|
||||
sed anchored on `>v$OLD</span>`, which silently no-op'd once the published
|
||||
page's value no longer matched the `old_version` passed for a release. Anchor
|
||||
on the stable `<span class="version-number">` instead and re-normalize whatever
|
||||
version is there to the new one, with an assert so a miss fails loudly. Same
|
||||
self-healing fix applied to the local-flow copy in `releases/version.sh`. The
|
||||
live wekan.fi install page was also corrected to the current version.
|
||||
Thanks to xet7 and Claude.
|
||||
|
||||
- [Make the remaining release version substitutions self-healing](https://github.com/wekan/wekan/commit/1e5ae8f64).
|
||||
Hardened the last `$OLD_VERSION`-anchored seds in `releases/version.sh` — the
|
||||
same fragile pattern that froze the Docker `ARG VERSION` and the install page.
|
||||
The snapcraft.yaml bundle download was release-critical (same class as the
|
||||
Docker bug: the snap downloads `wekan-<v>-<arch>.zip`, so a stale value ships
|
||||
the wrong bundle under the right name) and was stuck at v9.57; it now anchors
|
||||
on the `wekan-<v>-` / `releases/download/v<v>/` shapes and asserts. The
|
||||
sandstorm `appVersion` rewrite is now global and self-healing (the redundant
|
||||
`$OLD_NO_DOTS`-anchored fixup is dropped), and the Windows Offline.md doc links
|
||||
self-heal with a soft warning (cosmetic, so they must not fail the release).
|
||||
snapcraft.yaml and Offline.md were also corrected from their stale v9.57.
|
||||
Thanks to xet7 and Claude.
|
||||
|
||||
Thanks to above GitHub users for their contributions and translators for their translations.
|
||||
|
||||
# v9.62 2026-06-19 WeKan ® release
|
||||
|
||||
This release adds the following features:
|
||||
|
||||
- [Release All Platforms: Fix Docker image showing a stale Admin Panel version (image tagged vX reported v9.57)](https://github.com/wekan/wekan/commit/b30f4967c).
|
||||
The Admin Panel reads the WeKan version from the bundled `package.json`, which
|
||||
comes verbatim from the `wekan-<version>-<arch>.zip` the Dockerfile downloads
|
||||
and unzips into `/build`. The `docker` job never passed `--build-arg VERSION`,
|
||||
so every image was built against the Dockerfile's hardcoded `ARG VERSION`
|
||||
default — and that default was stuck at `9.57` because `releases/version.sh`
|
||||
rewrote it with a sed anchored on the *old* version number, which silently
|
||||
no-op'd whenever `old_version` did not match (e.g. the skipped 9.58 numbering).
|
||||
The result: images tagged v9.59/v9.60/v9.61 shipped the v9.57 bundle and
|
||||
reported 9.57 in the Admin Panel. Fixed three ways: the `docker` job now passes
|
||||
`--build-arg VERSION=${VERSION}` (the release version is authoritative); the
|
||||
`version.sh` Dockerfile rewrite now anchors on the `^ARG VERSION=` prefix and
|
||||
asserts the result, so the default can never go stale again; and a new
|
||||
pre-build guard downloads the release bundle and fails fast if its app
|
||||
`package.json` version does not match the release tag, before pushing a
|
||||
mislabeled image to the registries. Already-pushed v9.58–v9.61 images need a
|
||||
rebuild to carry their correct contents.
|
||||
Thanks to xet7 and Claude.
|
||||
|
||||
Thanks to above GitHub users for their contributions and translators for their translations.
|
||||
|
||||
# v9.61 2026-06-19 WeKan ® release
|
||||
|
||||
This release adds the following features:
|
||||
|
||||
+1
-1
@@ -7,7 +7,7 @@ LABEL org.opencontainers.image.source="https://github.com/wekan/wekan"
|
||||
# TARGETARCH and TARGETVARIANT are automatically provided by Docker Buildx
|
||||
ARG TARGETARCH
|
||||
ARG TARGETVARIANT
|
||||
ARG VERSION=9.57
|
||||
ARG VERSION=9.63
|
||||
ARG DEBIAN_FRONTEND=noninteractive
|
||||
|
||||
ENV BUILD_DEPS="apt-utils gnupg wget bzip2 g++ curl libarchive-tools build-essential git ca-certificates python3 unzip"
|
||||
|
||||
+1
-1
@@ -1,5 +1,5 @@
|
||||
appId: wekan-public/apps/77b94f60-dec9-0136-304e-16ff53095928
|
||||
appVersion: "v9.61.0"
|
||||
appVersion: "v9.63.0"
|
||||
files:
|
||||
userUploads:
|
||||
- README.md
|
||||
|
||||
@@ -10,7 +10,7 @@ This is without container (without Docker or Snap).
|
||||
|
||||
Right click and download files 1-4:
|
||||
|
||||
1. [wekan-9.57-win64.zip](https://github.com/wekan/wekan/releases/download/v9.57/wekan-9.57-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
|
||||
1. [wekan-9.63-win64.zip](https://github.com/wekan/wekan/releases/download/v9.63/wekan-9.63-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
|
||||
|
||||
2. [node.exe](https://nodejs.org/dist/latest-v24.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-9.57-win64.zip` , inside it is directory `bundle`, to it copy other files:
|
||||
7. Unzip `wekan-9.63-win64.zip` , inside it is directory `bundle`, to it copy other files:
|
||||
|
||||
```
|
||||
bundle (directory)
|
||||
|
||||
Generated
+2
-2
@@ -1,12 +1,12 @@
|
||||
{
|
||||
"name": "wekan",
|
||||
"version": "v9.61.0",
|
||||
"version": "v9.63.0",
|
||||
"lockfileVersion": 3,
|
||||
"requires": true,
|
||||
"packages": {
|
||||
"": {
|
||||
"name": "wekan",
|
||||
"version": "v9.61.0",
|
||||
"version": "v9.63.0",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"@aws-sdk/client-s3": "^3.1071.0",
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "wekan",
|
||||
"version": "v9.61.0",
|
||||
"version": "v9.63.0",
|
||||
"description": "Open-Source kanban",
|
||||
"private": true,
|
||||
"repository": {
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
|
||||
<head>
|
||||
<meta charset="utf8" />
|
||||
<title>WeKan REST API v9.61</title>
|
||||
<title>WeKan REST API v9.63</title>
|
||||
<!-- needed for adaptive design -->
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<style>
|
||||
@@ -423,7 +423,7 @@ data-styled.g139[id="sc-iIvZUO"]{content:"kAmnlO,"}/*!sc*/
|
||||
55.627 l 55.6165,55.627 -231.245496,231.24803 c -127.185,127.1864
|
||||
-231.5279,231.248 -231.873,231.248 -0.3451,0 -104.688,
|
||||
-104.0616 -231.873,-231.248 z
|
||||
" fill="currentColor"></path></g></svg></div></div><div class="sc-jtyQFi ldXCvc api-content"><div class="sc-eCQgVK jleRXN"><div class="sc-iCECmn lhRBUS"><div class="sc-hKVpXn kktglN api-info"><h1 class="sc-fuztkK sc-ctiVdb eRMVDe cBgvIi">Wekan REST API<!-- --> <span>(<!-- -->v9.61<!-- -->)</span></h1><p>Download OpenAPI specification<!-- -->:</p><div class="sc-iJSMbW sc-cBEgGa fiNpIH ewCFMV"></div><div data-role="redoc-summary" html="" class="sc-iJSMbW sc-cBEgGa fiNpIH ewCFMV"></div><div data-role="redoc-description" html="<p>The REST API allows you to control and extend Wekan with ease.</p>
|
||||
" fill="currentColor"></path></g></svg></div></div><div class="sc-jtyQFi ldXCvc api-content"><div class="sc-eCQgVK jleRXN"><div class="sc-iCECmn lhRBUS"><div class="sc-hKVpXn kktglN api-info"><h1 class="sc-fuztkK sc-ctiVdb eRMVDe cBgvIi">Wekan REST API<!-- --> <span>(<!-- -->v9.63<!-- -->)</span></h1><p>Download OpenAPI specification<!-- -->:</p><div class="sc-iJSMbW sc-cBEgGa fiNpIH ewCFMV"></div><div data-role="redoc-summary" html="" class="sc-iJSMbW sc-cBEgGa fiNpIH ewCFMV"></div><div data-role="redoc-description" html="<p>The REST API allows you to control and extend Wekan with ease.</p>
|
||||
<p>If you are an end-user and not a dev or a tester, <a href="https://github.com/wekan/wekan/issues/new">create an issue</a> to request new APIs.</p>
|
||||
<blockquote>
|
||||
<p>All API calls in the documentation are made using <code>curl</code>. However, you are free to use Java / Python / PHP / Golang / Ruby / Swift / Objective-C / Rust / Scala / C# or any other programming languages.</p>
|
||||
@@ -1965,7 +1965,7 @@ comment-only / worker members are rejected).</p>
|
||||
" class="sc-iJSMbW sc-cBEgGa sc-ciCrSJ fiNpIH dNfUH dDDioG"><p>Attachment not found</p>
|
||||
</div></button></div></div></div><div class="sc-jSppWd sc-gKkgUA fpMlmc bdQQyo"><div class="sc-fXwuWv fYxpnv"><button class="sc-jWMFtl jzaJhV"><span type="delete" class="sc-eEFuoE iINwyG http-verb delete">delete</span><span class="sc-FpjRO dsIRaZ">/api/attachment/delete/{attachmentId}</span><svg class="sc-dYjPD bQKUih" style="margin-right:-25px" version="1.1" viewBox="0 0 24 24" x="0" xmlns="http://www.w3.org/2000/svg" y="0" aria-hidden="true"><polygon points="17.3 8.3 12 13.6 6.7 8.3 5.3 9.7 12 16.4 18.7 9.7 "></polygon></svg></button><div aria-hidden="true" class="sc-fmtEmb tUxhh"><div class="sc-ljIcGq bAnPPh"><div html="" class="sc-iJSMbW sc-cBEgGa fiNpIH bAoMjv"></div><div tabindex="0" role="button"><div class="sc-jlJOIR PEJyb"><span></span>/api/attachment/delete/{attachmentId}</div></div></div></div></div></div></div></div></div><div class="sc-ekVkVN bjzTxL"></div></div></div>
|
||||
<script>
|
||||
const __redoc_state = {"menu":{"activeItemIdx":-1},"spec":{"data":{"openapi":"3.0.0","info":{"title":"Wekan REST API","version":"v9.61","description":"The REST API allows you to control and extend Wekan with ease.\n\nIf you are an end-user and not a dev or a tester, [create an issue](https://github.com/wekan/wekan/issues/new) to request new APIs.\n\n> All API calls in the documentation are made using `curl`. However, you are free to use Java / Python / PHP / Golang / Ruby / Swift / Objective-C / Rust / Scala / C# or any other programming languages.\n\n# Production Security Concerns\nWhen calling a production Wekan server, ensure it is running via HTTPS and has a valid SSL Certificate. The login method requires you to post your username and password in plaintext, which is why we highly suggest only calling the REST login api over HTTPS. Also, few things to note:\n\n* Only call via HTTPS\n* Implement a timed authorization token expiration strategy\n* Ensure the calling user only has permissions for what they are calling and no more\n"},"paths":{"/users/login":{"post":{"operationId":"login","summary":"Login with REST API","tags":["Login"],"requestBody":{"content":{"application/json":{"schema":{"type":"object","required":["username","password"],"properties":{"username":{"description":"Your username\n","type":"string"},"password":{"description":"Your password\n","type":"string","format":"password"}}}},"application/x-www-form-urlencoded":{"schema":{"type":"object","required":["username","password"],"properties":{"username":{"description":"Your username\n","type":"string"},"password":{"description":"Your password\n","type":"string","format":"password"}}}}},"description":"Login credentials","required":true},"responses":{"200":{"description":"Successful authentication","content":{"*/*":{"schema":{"type":"object","required":["id","token","tokenExpires"],"properties":{"id":{"type":"string","description":"User ID"},"token":{"type":"string","description":"Authentication token\n"},"tokenExpires":{"type":"string","format":"date-time","description":"Token expiration date\n"}}}}}},"400":{"description":"Error in authentication\n","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"reason":{"type":"string"}}}}}},"default":{"description":"Error in authentication\n"}}}},"/users/register":{"post":{"operationId":"register","summary":"Register with REST API","description":"Notes:\n - You will need to provide the token for any of the authenticated methods.\n","tags":["Login"],"requestBody":{"content":{"application/x-www-form-urlencoded":{"schema":{"type":"object","properties":{"username":{"description":"Your username\n","type":"string"},"password":{"description":"Your password\n","type":"string","format":"password"},"email":{"description":"Your email\n","type":"string"}},"required":["username","password","email"]}}},"required":true},"responses":{"200":{"description":"Successful registration","content":{"*/*":{"schema":{"items":{"properties":{"id":{"type":"string"},"token":{"type":"string"},"tokenExpires":{"type":"string"}}}}}}},"400":{"description":"Error in registration\n","content":{"*/*":{"schema":{"items":{"properties":{"error":{"type":"number"},"reason":{"type":"string"}}}}}}},"default":{"description":"Error in registration\n"}}}},"/api/admin/attachment-settings":{"get":{"operationId":"get_attachment_settings","summary":"Get the attachment storage / upload-block settings (GlobalAdmin)","description":"Only the global admin can call this. Returns the Admin Panel >\n Attachments settings document, including `limitSettings.attachmentsUploadBlocked`\n and `limitSettings.avatarsUploadBlocked` plus the size limits. Cloud-storage\n secret keys (S3 secretAccessKey, Azure accountKey/connectionString, GCS\n credentials) are masked and never returned; a boolean `<field>Set` marker\n shows whether a value exists.\n","tags":["AttachmentStorageSettings","Settings"],"security":[{"UserSecurity":[]}],"responses":{"200":{"description":"200 response","content":{"application/json":{"schema":{"type":"Object"}}}}}},"put":{"operationId":"update_attachment_settings","summary":"Update the attachment storage / upload-block settings (GlobalAdmin)","description":"Only the global admin can call this. The request body is a\n partial settings object (for example\n `{\"limitSettings\": {\"avatarsUploadBlocked\": true}}`). It is applied through\n the same update path as the `updateAttachmentStorageSettings` Meteor method,\n so validation and `$set` semantics are identical: cloud-storage secrets left\n blank are preserved. The masked, updated settings document is returned.\n","tags":["AttachmentStorageSettings","Settings"],"security":[{"UserSecurity":[]}],"responses":{"200":{"description":"200 response","content":{"application/json":{"schema":{"type":"Object"}}}}}}},"/api/admin/domains":{"get":{"operationId":"get_admin_domains","summary":"List email domains with their user counts (GlobalAdmin)","description":"Only the gLine truncated
|
||||
const __redoc_state = {"menu":{"activeItemIdx":-1},"spec":{"data":{"openapi":"3.0.0","info":{"title":"Wekan REST API","version":"v9.63","description":"The REST API allows you to control and extend Wekan with ease.\n\nIf you are an end-user and not a dev or a tester, [create an issue](https://github.com/wekan/wekan/issues/new) to request new APIs.\n\n> All API calls in the documentation are made using `curl`. However, you are free to use Java / Python / PHP / Golang / Ruby / Swift / Objective-C / Rust / Scala / C# or any other programming languages.\n\n# Production Security Concerns\nWhen calling a production Wekan server, ensure it is running via HTTPS and has a valid SSL Certificate. The login method requires you to post your username and password in plaintext, which is why we highly suggest only calling the REST login api over HTTPS. Also, few things to note:\n\n* Only call via HTTPS\n* Implement a timed authorization token expiration strategy\n* Ensure the calling user only has permissions for what they are calling and no more\n"},"paths":{"/users/login":{"post":{"operationId":"login","summary":"Login with REST API","tags":["Login"],"requestBody":{"content":{"application/json":{"schema":{"type":"object","required":["username","password"],"properties":{"username":{"description":"Your username\n","type":"string"},"password":{"description":"Your password\n","type":"string","format":"password"}}}},"application/x-www-form-urlencoded":{"schema":{"type":"object","required":["username","password"],"properties":{"username":{"description":"Your username\n","type":"string"},"password":{"description":"Your password\n","type":"string","format":"password"}}}}},"description":"Login credentials","required":true},"responses":{"200":{"description":"Successful authentication","content":{"*/*":{"schema":{"type":"object","required":["id","token","tokenExpires"],"properties":{"id":{"type":"string","description":"User ID"},"token":{"type":"string","description":"Authentication token\n"},"tokenExpires":{"type":"string","format":"date-time","description":"Token expiration date\n"}}}}}},"400":{"description":"Error in authentication\n","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"reason":{"type":"string"}}}}}},"default":{"description":"Error in authentication\n"}}}},"/users/register":{"post":{"operationId":"register","summary":"Register with REST API","description":"Notes:\n - You will need to provide the token for any of the authenticated methods.\n","tags":["Login"],"requestBody":{"content":{"application/x-www-form-urlencoded":{"schema":{"type":"object","properties":{"username":{"description":"Your username\n","type":"string"},"password":{"description":"Your password\n","type":"string","format":"password"},"email":{"description":"Your email\n","type":"string"}},"required":["username","password","email"]}}},"required":true},"responses":{"200":{"description":"Successful registration","content":{"*/*":{"schema":{"items":{"properties":{"id":{"type":"string"},"token":{"type":"string"},"tokenExpires":{"type":"string"}}}}}}},"400":{"description":"Error in registration\n","content":{"*/*":{"schema":{"items":{"properties":{"error":{"type":"number"},"reason":{"type":"string"}}}}}}},"default":{"description":"Error in registration\n"}}}},"/api/admin/attachment-settings":{"get":{"operationId":"get_attachment_settings","summary":"Get the attachment storage / upload-block settings (GlobalAdmin)","description":"Only the global admin can call this. Returns the Admin Panel >\n Attachments settings document, including `limitSettings.attachmentsUploadBlocked`\n and `limitSettings.avatarsUploadBlocked` plus the size limits. Cloud-storage\n secret keys (S3 secretAccessKey, Azure accountKey/connectionString, GCS\n credentials) are masked and never returned; a boolean `<field>Set` marker\n shows whether a value exists.\n","tags":["AttachmentStorageSettings","Settings"],"security":[{"UserSecurity":[]}],"responses":{"200":{"description":"200 response","content":{"application/json":{"schema":{"type":"Object"}}}}}},"put":{"operationId":"update_attachment_settings","summary":"Update the attachment storage / upload-block settings (GlobalAdmin)","description":"Only the global admin can call this. The request body is a\n partial settings object (for example\n `{\"limitSettings\": {\"avatarsUploadBlocked\": true}}`). It is applied through\n the same update path as the `updateAttachmentStorageSettings` Meteor method,\n so validation and `$set` semantics are identical: cloud-storage secrets left\n blank are preserved. The masked, updated settings document is returned.\n","tags":["AttachmentStorageSettings","Settings"],"security":[{"UserSecurity":[]}],"responses":{"200":{"description":"200 response","content":{"application/json":{"schema":{"type":"Object"}}}}}}},"/api/admin/domains":{"get":{"operationId":"get_admin_domains","summary":"List email domains with their user counts (GlobalAdmin)","description":"Only the gLine truncated
|
||||
|
||||
var container = document.getElementById('redoc');
|
||||
Redoc.hydrate(__redoc_state, container);
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
swagger: '2.0'
|
||||
info:
|
||||
title: Wekan REST API
|
||||
version: v9.61
|
||||
version: v9.63
|
||||
description: |
|
||||
The REST API allows you to control and extend Wekan with ease.
|
||||
|
||||
|
||||
@@ -56,14 +56,22 @@ sedi "s|<span id=\"node-version\">[^<]*</span>|<span id=\"node-version\">$NODE_V
|
||||
sedi "s|<span id=\"npm-version\">[^<]*</span>|<span id=\"npm-version\">$NPM_VERSION</span>|g" $WEBDIR/install/index.html
|
||||
|
||||
# $WEBDIR/install/index.html
|
||||
# The version appears inside a specific HTML span tag.
|
||||
# This pattern is already precise enough to match only the WeKan version.
|
||||
sedi "s|>v$OLD<\/span>|>v$NEW<\/span>|g" $WEBDIR/install/index.html
|
||||
# The WeKan version lives in <span class="version-number">v<x></span>.
|
||||
# Anchor on the class (the stable identifier), NOT on the old version number,
|
||||
# so this re-normalizes whatever version is currently there to v$NEW. The old
|
||||
# ">v$OLD</span>" pattern silently no-op'd whenever $OLD did not match the
|
||||
# (possibly already stale) value on the page, which is how the published page
|
||||
# got stuck at an old version while every release passed a newer $OLD that no
|
||||
# longer matched. This self-healing form recovers from any stale value.
|
||||
sedi -E "s#(<span class=\"version-number\">)v[0-9][^<]*(</span>)#\1v${NEW}\2#g" $WEBDIR/install/index.html
|
||||
if ! grep -qF "<span class=\"version-number\">v${NEW}</span>" $WEBDIR/install/index.html; then
|
||||
echo "Error: failed to set version-number span to v${NEW} in $WEBDIR/install/index.html." >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Also update Meteor and Node.js versions in the <h2 class="fw-bold"> line
|
||||
sedi "s|\(Meteor \)[^,]*,|\1${METEOR_VERSION},|g" $WEBDIR/install/index.html
|
||||
sedi "s|\(Node\.js \)[0-9][0-9]*\.[x0-9a-zA-Z.-]*|\1${NODE_VERSION}|g" $WEBDIR/install/index.html
|
||||
sedi "s|>v$OLD<\/span>|>v$NEW<\/span>|g" $WEBDIR/install/index.html
|
||||
|
||||
# api/index.html
|
||||
# The version appears in href attributes and as link text, e.g.:
|
||||
|
||||
+55
-9
@@ -402,16 +402,60 @@ version_bump_logic() {
|
||||
echo "Error: failed to set snap version to '${NEW_VERSION}' in snapcraft.yaml." >&2
|
||||
exit 1
|
||||
fi
|
||||
sedi "s|v$OLD_VERSION/|v$NEW_VERSION/|g" snapcraft.yaml
|
||||
sedi "s|wekan-$OLD_VERSION-|wekan-$NEW_VERSION-|g" snapcraft.yaml
|
||||
# Re-point the bundle the snap downloads to v$NEW_VERSION. Anchor on the stable
|
||||
# "wekan-<v>-" and "releases/download/v<v>/" shapes, NOT on $OLD_VERSION: the
|
||||
# snap is RELEASE-CRITICAL exactly like the Docker image — it downloads
|
||||
# wekan-<v>-<arch>.zip here, so if these stayed at an old version (which the
|
||||
# $OLD_VERSION-anchored form did whenever $OLD did not match) the snap would be
|
||||
# NAMED v$NEW_VERSION (via the version: line above) but SHIP the old bundle and
|
||||
# report the old version. Self-healing + assert so any miss fails the release.
|
||||
sedi -E "s#wekan-[0-9]+\.[0-9]+(\.[0-9]+)?-#wekan-${NEW_VERSION}-#g" snapcraft.yaml
|
||||
sedi -E "s#(releases/download/)v[0-9]+\.[0-9]+(\.[0-9]+)?/#\1v${NEW_VERSION}/#g" snapcraft.yaml
|
||||
if grep -qE "wekan-[0-9]+\.[0-9]+(\.[0-9]+)?-" snapcraft.yaml \
|
||||
&& ! grep -qF "wekan-${NEW_VERSION}-" snapcraft.yaml; then
|
||||
echo "Error: failed to set the WeKan bundle version to ${NEW_VERSION} in snapcraft.yaml." >&2
|
||||
exit 1
|
||||
fi
|
||||
if grep -qE "releases/download/v[0-9]" snapcraft.yaml \
|
||||
&& ! grep -qF "releases/download/v${NEW_VERSION}/" snapcraft.yaml; then
|
||||
echo "Error: failed to set the release-download URL to v${NEW_VERSION} in snapcraft.yaml." >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
sedi "0,/appVersion = [0-9]\+/s/appVersion = [0-9]\+/appVersion = ${NEW_NO_DOTS}/" sandstorm-pkgdef.capnp
|
||||
sedi "0,/appMarketingVersion = (defaultText = \"[^\"]*\")/s/appMarketingVersion = (defaultText = \"[^\"]*\")/appMarketingVersion = (defaultText = \"${NEW_VERSION}~${TODAY}\")/" sandstorm-pkgdef.capnp
|
||||
sedi "s|appVersion = $OLD_NO_DOTS,|appVersion = $NEW_NO_DOTS,|g" sandstorm-pkgdef.capnp
|
||||
# Both anchor on the field name and re-normalize whatever value is there to the
|
||||
# new version (NOT on the old value), so they self-heal from any stale state.
|
||||
# Global, not first-match, and the old separate "appVersion = $OLD_NO_DOTS,"
|
||||
# fixup is dropped — that $OLD-anchored line silently no-op'd on a mismatch and
|
||||
# is redundant now that this rewrites every appVersion occurrence.
|
||||
sedi -E "s/appVersion = [0-9]+/appVersion = ${NEW_NO_DOTS}/g" sandstorm-pkgdef.capnp
|
||||
sedi -E "s/appMarketingVersion = \(defaultText = \"[^\"]*\"\)/appMarketingVersion = (defaultText = \"${NEW_VERSION}~${TODAY}\")/g" sandstorm-pkgdef.capnp
|
||||
if ! grep -qF "appVersion = ${NEW_NO_DOTS}" sandstorm-pkgdef.capnp; then
|
||||
echo "Error: failed to set 'appVersion = ${NEW_NO_DOTS}' in sandstorm-pkgdef.capnp." >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
sedi "s|ARG VERSION=$OLD_VERSION|ARG VERSION=$NEW_VERSION|g" Dockerfile
|
||||
sedi "s|wekan-$OLD_VERSION|wekan-$NEW_VERSION|g" docs/Platforms/Propietary/Windows/Offline.md
|
||||
sedi "s|/v$OLD_VERSION/|/v$NEW_VERSION/|g" docs/Platforms/Propietary/Windows/Offline.md
|
||||
# Anchor on the `ARG VERSION=` prefix, NOT on the old version number, so this
|
||||
# always rewrites the default to the new version even if OLD_VERSION was passed
|
||||
# wrong (e.g. a skipped point release). A stale default here means every Docker
|
||||
# image downloads that version's wekan-<v>-<arch>.zip and reports the wrong
|
||||
# version in the Admin Panel. release-all.yml also passes --build-arg VERSION,
|
||||
# but keep this in sync so manual `docker build .` produces the right image too.
|
||||
sedi -E "s|^ARG VERSION=.*|ARG VERSION=$NEW_VERSION|g" Dockerfile
|
||||
if ! grep -qxF "ARG VERSION=$NEW_VERSION" Dockerfile; then
|
||||
echo "Error: failed to set 'ARG VERSION=$NEW_VERSION' in Dockerfile." >&2
|
||||
exit 1
|
||||
fi
|
||||
# Documentation (Windows offline-install guide): same self-healing anchors as
|
||||
# snapcraft.yaml so the doc's download links re-point to v$NEW_VERSION from any
|
||||
# stale value. Only warn (don't fail the release) on a miss — a stale doc link
|
||||
# is cosmetic, unlike the snap/Docker bundles above.
|
||||
OFFLINE_DOC="docs/Platforms/Propietary/Windows/Offline.md"
|
||||
sedi -E "s#wekan-[0-9]+\.[0-9]+(\.[0-9]+)?-#wekan-${NEW_VERSION}-#g" "$OFFLINE_DOC"
|
||||
sedi -E "s#(releases/download/)v[0-9]+\.[0-9]+(\.[0-9]+)?/#\1v${NEW_VERSION}/#g" "$OFFLINE_DOC"
|
||||
if grep -qE "wekan-[0-9]+\.[0-9]+(\.[0-9]+)?-" "$OFFLINE_DOC" \
|
||||
&& ! grep -qF "wekan-${NEW_VERSION}-" "$OFFLINE_DOC"; then
|
||||
echo "[WARN] $OFFLINE_DOC still references an old wekan-<version> bundle; expected ${NEW_VERSION}." >&2
|
||||
fi
|
||||
|
||||
# 7. Download dependency artifacts from upstream to ~/Lataukset for the optional
|
||||
# USE_LOCAL_DEP_VERSIONS offline mode. The builds themselves fetch from upstream too.
|
||||
@@ -446,7 +490,9 @@ version_bump_logic() {
|
||||
|
||||
(cd ../w/wekan.fi && git pull)
|
||||
sedi "s|<span id=\"meteor-version\">[^<]*</span>|<span id=\"meteor-version\">$METEOR_VER</span>|g" "$INSTALL_PAGE"
|
||||
sedi "s|<span class=\"version-number\">v${OLD_VERSION}</span>|<span class=\"version-number\">v${NEW_VERSION}</span>|g" "$INSTALL_PAGE"
|
||||
# Anchor on the version-number class, not on $OLD_VERSION, so a stale value on
|
||||
# the page still gets re-normalized to v$NEW_VERSION (see release-website.sh).
|
||||
sedi -E "s#(<span class=\"version-number\">)v[0-9][^<]*(</span>)#\1v${NEW_VERSION}\2#g" "$INSTALL_PAGE"
|
||||
(
|
||||
cd ../w/wekan.fi
|
||||
git add --all
|
||||
|
||||
@@ -22,10 +22,10 @@ const pkgdef :Spk.PackageDefinition = (
|
||||
appTitle = (defaultText = "Wekan"),
|
||||
# The name of the app as it is displayed to the user.
|
||||
|
||||
appVersion = 961,
|
||||
appVersion = 963,
|
||||
# Increment this for every release.
|
||||
|
||||
appMarketingVersion = (defaultText = "9.61~2026-06-19"),
|
||||
appMarketingVersion = (defaultText = "9.63~2026-06-19"),
|
||||
# Human-readable presentation of the app version.
|
||||
|
||||
minUpgradableAppVersion = 0,
|
||||
|
||||
+4
-4
@@ -1,5 +1,5 @@
|
||||
name: wekan
|
||||
version: '9.61'
|
||||
version: '9.63'
|
||||
base: core26
|
||||
build-base: devel
|
||||
confinement: strict
|
||||
@@ -194,14 +194,14 @@ parts:
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
WEKAN_ZIP="wekan-9.57-${WEKAN_ARCH}.zip"
|
||||
WEKAN_ZIP="wekan-9.63-${WEKAN_ARCH}.zip"
|
||||
NODE_TAR="node-v24.17.0-linux-${NODE_ARCH}.tar.xz"
|
||||
echo "Cleaning environment first"
|
||||
rm -rf .build
|
||||
mkdir .build
|
||||
cd .build
|
||||
#wget https://github.com/wekan/wekan/releases/download/v9.57/wekan-9.57-amd64.zip
|
||||
wget "https://github.com/wekan/wekan/releases/download/v9.57/${WEKAN_ZIP}"
|
||||
#wget https://github.com/wekan/wekan/releases/download/v9.63/wekan-9.63-amd64.zip
|
||||
wget "https://github.com/wekan/wekan/releases/download/v9.63/${WEKAN_ZIP}"
|
||||
unzip "${WEKAN_ZIP}"
|
||||
rm "${WEKAN_ZIP}"
|
||||
# Fix: bcrypt 5.0.1 (Meteor accounts-password) ships node-addon-api@3
|
||||
|
||||
Reference in new issue
Block a user