website, branch main The site of tala.run: a Vue frontend and an ASP.NET Core API. Merge pull request #57 from Progmasoft/ci/codeql-pin 2026-11-09T21:45:05+00:00 Leitwolf 2026-11-09T21:45:05+00:00 cc6ca15df51dea156cac1ea697fb620e9b6f08ca Pin the CodeQL action to its v4.38.2 release 
Pin the CodeQL action to its v4.38.2 release
 Merge remote-tracking branch 'origin/main' into ci/codeql-pin 2026-11-08T22:18:33+00:00 Leitwolf11 2026-11-08T22:18:33+00:00 8d1af706829bd802d215d385922e1d245bf9349b 






Merge pull request #56 from Progmasoft/docs/drop-xide-faq
2026-11-08T22:17:50+00:00

Leitwolf

2026-11-08T22:17:50+00:00

6e93a0fb9406ee321ee9ed6d960bd7fa02c34e76

Drop Xide from the IDE answer of the Overview FAQ




Drop Xide from the IDE answer of the Overview FAQ






Pin the CodeQL action to its v4.38.2 release
2026-11-08T21:42:31+00:00

Leitwolf11

2026-11-08T21:42:31+00:00

5552879a1e328711319051a9b074b5769f69564e

The init and analyze steps were pinned to 7999b86c, a commit no release tag
points at, with a "# v4" comment that names another commit (zizmor
ref-version-mismatch, two code-scanning alerts). Both steps now use
2892aa5e, the commit of v4.38.2, with that exact version as the comment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>





The init and analyze steps were pinned to 7999b86c, a commit no release tag
points at, with a "# v4" comment that names another commit (zizmor
ref-version-mismatch, two code-scanning alerts). Both steps now use
2892aa5e, the commit of v4.38.2, with that exact version as the comment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>







Drop Xide from the IDE answer of the Overview FAQ
2026-11-08T15:48:41+00:00

Leitwolf11

2026-11-08T15:48:41+00:00

20d8210a90fcb1e13a36487569e9a53991e16e92

Xide is no longer developed as of 2026-11-08 (Progmasoft/xide#29), so
the answer to "Does Tala require a particular IDE?" no longer calls it a
future interface. In all four languages the answer now says only that
the supported workflow uses command-line tools on Windows, macOS and
Linux.





Xide is no longer developed as of 2026-11-08 (Progmasoft/xide#29), so
the answer to "Does Tala require a particular IDE?" no longer calls it a
future interface. In all four languages the answer now says only that
the supported workflow uses command-line tools on Windows, macOS and
Linux.







Merge pull request #55 from Progmasoft/ops/cloudflare-analytics
2026-11-06T06:36:33+00:00

Leitwolf

2026-11-06T06:36:33+00:00

9660d2c5f0bda5d666ed076a0e18d5cb2dbe881d

Let Cloudflare Web Analytics run on the Tala sites




Let Cloudflare Web Analytics run on the Tala sites






Merge pull request #54 from Progmasoft/ops/tazel-redirect
2026-11-06T06:30:47+00:00

Leitwolf

2026-11-06T06:30:47+00:00

fc3246f3eb404bc2c3132691d1161a95c5bfac76

Redirect tazel.tala.run to tazel.net for good




Redirect tazel.tala.run to tazel.net for good






Describe the Web Analytics exception in the architecture and runbook
2026-11-06T06:30:09+00:00

Leitwolf11

2026-11-06T06:30:09+00:00

7d1ef624fd8842acab54fce6373b4ad2bbb25eb9

The four hosts of the site now allow Cloudflare's Web Analytics beacon,
but ARCHITECTURE.md and OPERATIONS.md still said the policy blocks every
script an intermediary adds. Both now name the beacon, where it loads
from and where it reports, and keep the forum placeholder's same-origin
policy apart.





The four hosts of the site now allow Cloudflare's Web Analytics beacon,
but ARCHITECTURE.md and OPERATIONS.md still said the policy blocks every
script an intermediary adds. Both now name the beacon, where it loads
from and where it reports, and keep the forum placeholder's same-origin
policy apart.







Let Cloudflare Web Analytics run on the Tala sites
2026-11-06T05:00:18+00:00

Leitwolf11

2026-11-06T05:00:18+00:00

e13d8e3d85fed0d8b8421c624dac2e69e3398cab

Cloudflare adds its Web Analytics beacon to each page it serves. The
policies of tala.run, talac.tala.run, talafmt.tala.run and
talalint.tala.run fell back to default-src 'self' for scripts, so the
browser refused the beacon. They now allow scripts from
static.cloudflareinsights.com and connections to cloudflareinsights.com;
the beacon reports to /cdn-cgi/rum on the same host.





Cloudflare adds its Web Analytics beacon to each page it serves. The
policies of tala.run, talac.tala.run, talafmt.tala.run and
talalint.tala.run fell back to default-src 'self' for scripts, so the
browser refused the beacon. They now allow scripts from
static.cloudflareinsights.com and connections to cloudflareinsights.com;
the beacon reports to /cdn-cgi/rum on the same host.







Check the tazel.tala.run redirect and describe it in the documents
2026-11-06T04:58:09+00:00

Leitwolf11

2026-11-06T04:58:09+00:00

1439b240a8231c5206e3c8d4f245493a076f2841

The integrity tests still expected tazel.tala.run to serve the Vue build
with its own robots.txt and sitemap.xml. They now count four app-shell
hosts and check the redirect itself: the two former pages go to their
pages under tazel.net/docs/reference/ with the query string, other docs
paths to tazel.net/docs, everything else to the same path, the /docs/
prefix is a plain one so the regular expression is reached, and HSTS
stays.

OPERATIONS.md and ARCHITECTURE.md list tazel.tala.run as a permanent
redirect instead of a documentation site.





The integrity tests still expected tazel.tala.run to serve the Vue build
with its own robots.txt and sitemap.xml. They now count four app-shell
hosts and check the redirect itself: the two former pages go to their
pages under tazel.net/docs/reference/ with the query string, other docs
paths to tazel.net/docs, everything else to the same path, the /docs/
prefix is a plain one so the regular expression is reached, and HSTS
stays.

OPERATIONS.md and ARCHITECTURE.md list tazel.tala.run as a permanent
redirect instead of a documentation site.