Merge pull request 'Bump the version to 0.3.4 and write the changelog entry (MIL-011)' (#93) from release-0-3-4-version-and-changelog into main

Reviewed-on: #93

CHANGELOG.md

@@ -13,6 +13,8 @@ file.
 
 ## [Unreleased]
 
+## [0.3.4] - 2026-10-13
+
 ### Added
 
 - Gitea workflows: Quality (shellcheck and shfmt through the shared reusable
@@ -21,3 +23,18 @@ file.
   shared Publish wiki workflow.
 - `switch_case_indent` for `*.sh` in `.editorconfig`, so `shfmt` accepts the
   existing layout of `case` branches.
+- `TOKEN_FOR_GITEA_WIKI` is accepted in `.env`: an optional Gitea token with
+  the repository write scope only, for publishing the wiki. It is checked like
+  the other tokens, kept out of every message and never used or asked for, so
+  one `.env` can serve both RepoFoundry and the wiki publishing.
+- The wiki in English, Danish and Bahasa Malaysia: Getting started, SSH and
+  tokens, Access tokens, Updating the framework and Troubleshooting.
+
+### Changed
+
+- The guide for creating the access tokens moved from `howto/` to the wiki
+  page Access tokens, with its pictures and a Danish and a Bahasa Malaysia
+  translation.
+- The README, the wiki and `.env.example` say which credentials are required:
+  `GITEA_TOKEN` always, `GITHUB_PAT` and `GITHUB_USER` only when GitHub is
+  chosen, and `TOKEN_FOR_GITEA_WIKI` never.

src/lib/constants.sh

@@ -8,7 +8,7 @@
 # shellcheck disable=SC2034  # read and written by the other library files
 
 readonly PROJECT_NAME="${REPOFOUNDRY_NAME:-RepoFoundry}"
-readonly VERSION="0.3.3"
+readonly VERSION="0.3.4"
 readonly EXIT_FAILURE=1
 readonly EXIT_USAGE=2
 readonly MAX_VALUE_LENGTH=2048

tests/test-security.sh

@@ -103,7 +103,7 @@ test_usage_errors() {
   assert_contains "help shows exit codes" "$OUT" "Exit codes"
   run_cli "" --version
   assert_status "version" 0 "$STATUS"
-  assert_contains "version output" "$OUT" "RepoFoundry 0.3.3"
+  assert_contains "version output" "$OUT" "RepoFoundry 0.3.4"
 }
 
 test_warns_when_env_is_not_ignored_by_git() {