<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb, branch fix/tala-names</title>
<subtitle>The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/'/>
<entry>
<title>Call the language Tala on the Progmasoft and ViGet pages</title>
<updated>2026-10-12T03:19:10+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-12T03:19:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=b71e93b547e9f6425cc83b121f01e7d82b88079f'/>
<id>b71e93b547e9f6425cc83b121f01e7d82b88079f</id>
<content type='text'>
The language Visual X# is now Tala. The Progmasoft home page, the ViGet
pages, the dashboard and the two footers name it so in the four languages of
the site; the project file is BUILD.kts, and the source link leads to
Progmasoft/tala. The README, the operations and localization documents and
the issue templates follow.

The localization document said that a left-to-right mark follows the name of
the language in Hebrew text. That was for the `#` of the old name; the
sentence now speaks of names that end in a symbol.

The links to xsharp-lang.xyz stay: the language site is still served there.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The language Visual X# is now Tala. The Progmasoft home page, the ViGet
pages, the dashboard and the two footers name it so in the four languages of
the site; the project file is BUILD.kts, and the source link leads to
Progmasoft/tala. The README, the operations and localization documents and
the issue templates follow.

The localization document said that a left-to-right mark follows the name of
the language in Hebrew text. That was for the `#` of the old name; the
sentence now speaks of names that end in a symbol.

The links to xsharp-lang.xyz stay: the language site is still served there.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #32 from Progmasoft/ci/renovate</title>
<updated>2026-10-10T21:15:29+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-10-10T21:15:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=84541a742a7dcd5d067e7532b33e61eaf3e0174d'/>
<id>84541a742a7dcd5d067e7532b33e61eaf3e0174d</id>
<content type='text'>
Hand version updates to Renovate</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Hand version updates to Renovate</pre>
</div>
</content>
</entry>
<entry>
<title>Merge main into the Renovate branch</title>
<updated>2026-10-10T20:16:50+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-10T20:16:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=107a257bb5313828ca5a36e4f1c2963dfb24b294'/>
<id>107a257bb5313828ca5a36e4f1c2963dfb24b294</id>
<content type='text'>
main gained the workflow analysis change, which adds a line to the
checkout step right above the action whose version comment this branch
corrects. Both changes are kept: the checkout does not persist its
credentials, and the comment names v4.9.0.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
main gained the workflow analysis change, which adds a line to the
checkout step right above the action whose version comment this branch
corrects. Both changes are kept: the checkout does not persist its
credentials, and the comment names v4.9.0.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #31 from Progmasoft/ci/analysis-tools</title>
<updated>2026-10-10T20:01:00+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-10-10T20:01:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=25ceeecda724a277a174e7cc7e4402cd69c85897'/>
<id>25ceeecda724a277a174e7cc7e4402cd69c85897</id>
<content type='text'>
Add workflow analysis</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add workflow analysis</pre>
</div>
</content>
</entry>
<entry>
<title>Name the pinned version of the dependency review action</title>
<updated>2026-10-10T19:35:08+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-10T19:35:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=65f4b4f309958def71b9b8956c06d0d55b75e700'/>
<id>65f4b4f309958def71b9b8956c06d0d55b75e700</id>
<content type='text'>
The action is pinned to the commit of v4.9.0, and the comment beside
the pin said v4. Renovate reads the comment as the version in use and
looked for a tag named v5 to update to; the action has v5.0.0 and no
v5, so the lookup failed and Renovate warned about it. The comment now
names the version the commit is.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The action is pinned to the commit of v4.9.0, and the comment beside
the pin said v4. Renovate reads the comment as the version in use and
looked for a tag named v5 to update to; the action has v5.0.0 and no
v5, so the lookup failed and Renovate warned about it. The comment now
names the version the commit is.
</pre>
</div>
</content>
</entry>
<entry>
<title>Hand version updates to Renovate</title>
<updated>2026-10-10T19:30:30+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-10T19:30:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=7d874044576d6a10c3a6cbec44e70231ddfbada5'/>
<id>7d874044576d6a10c3a6cbec44e70231ddfbada5</id>
<content type='text'>
Renovate proposes the version updates of this repository from now on.
It watches what Dependabot watched, looks once a week, takes a release
a week after it is published, opens one pull request for each kind of
dependency with at most two open, and rebases a pull request only when
it conflicts. A dashboard issue lists what is pending.

The Dependabot configuration is removed, which turns its version
updates off. Dependabot keeps its alerts and its security updates,
which are repository settings. Renovate does not open its own pull
requests for vulnerabilities, so one advisory does not get two fixes.

The configuration passes Renovate's validator and takes effect when
the Renovate app is installed on the repository.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Renovate proposes the version updates of this repository from now on.
It watches what Dependabot watched, looks once a week, takes a release
a week after it is published, opens one pull request for each kind of
dependency with at most two open, and rebases a pull request only when
it conflicts. A dashboard issue lists what is pending.

The Dependabot configuration is removed, which turns its version
updates off. Dependabot keeps its alerts and its security updates,
which are repository settings. Renovate does not open its own pull
requests for vulnerabilities, so one advisory does not get two fixes.

The configuration passes Renovate's validator and takes effect when
the Renovate app is installed on the repository.
</pre>
</div>
</content>
</entry>
<entry>
<title>Leave out the Scorecard workflow</title>
<updated>2026-10-10T17:26:52+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-10T17:26:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=04622baa18a5d52b60ec0f7ea882896956a91c3a'/>
<id>04622baa18a5d52b60ec0f7ea882896956a91c3a</id>
<content type='text'>
The owner decided against running OpenSSF Scorecard here. The workflow
added by the commit before this one is removed; nothing else changes.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The owner decided against running OpenSSF Scorecard here. The workflow
added by the commit before this one is removed; nothing else changes.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add workflow and repository analysis</title>
<updated>2026-10-10T17:23:08+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-10T17:23:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=525f3c0566247bbb6a81b5a2e1488147688c089a'/>
<id>525f3c0566247bbb6a81b5a2e1488147688c089a</id>
<content type='text'>
zizmor audits the workflows themselves for what makes a workflow
unsafe, and uploads what it finds to code scanning. Its first run here
found one thing, 6 times: a checkout that leaves the job's token in
the checked-out repository, where any later step can read it. No
workflow pushes or needs the token after the checkout, so every checkout
now sets persist-credentials to false, and zizmor reports nothing.

OpenSSF Scorecard grades how the repository is kept: branch protection,
pinned dependencies, token permissions and the like. It runs on the
default branch and weekly, publishes its score and uploads its findings to
code scanning.

Every new action is pinned to a commit, each job names the permissions
it needs, and no new workflow has a default permission.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
zizmor audits the workflows themselves for what makes a workflow
unsafe, and uploads what it finds to code scanning. Its first run here
found one thing, 6 times: a checkout that leaves the job's token in
the checked-out repository, where any later step can read it. No
workflow pushes or needs the token after the checkout, so every checkout
now sets persist-credentials to false, and zizmor reports nothing.

OpenSSF Scorecard grades how the repository is kept: branch protection,
pinned dependencies, token permissions and the like. It runs on the
default branch and weekly, publishes its score and uploads its findings to
code scanning.

Every new action is pinned to a commit, each job names the permissions
it needs, and no new workflow has a default permission.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #28 from Progmasoft/feature/durable-account-store</title>
<updated>2026-10-07T04:09:39+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-10-07T04:09:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=111a6175e0a92808ddc2a47088fa9858001eeed9'/>
<id>111a6175e0a92808ddc2a47088fa9858001eeed9</id>
<content type='text'>
Keep accounts and sessions in PostgreSQL</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Keep accounts and sessions in PostgreSQL</pre>
</div>
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'origin/main' into feature/durable-account-store</title>
<updated>2026-10-07T00:57:11+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-07T00:57:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=a1383b688d3d2159e3ba525682180f9d5a4a2c80'/>
<id>a1383b688d3d2159e3ba525682180f9d5a4a2c80</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
