TirSystem-BashScript/repo-foundry

Fork 0

Files

T

Tirsvad 54caec9cc7

Quality checks / quality-checks (pull_request) Successful in 27s

Details

Quality / quality (pull_request) Successful in 27s

Details

Bump the version to 0.3.4 and write its changelog entry

VERSION and the --version check say 0.3.4. The entries of Unreleased move
under a dated 0.3.4 entry, with TOKEN_FOR_GITEA_WIKI, the wiki in three
languages, the access-token guide in the wiki and the credential rules.

Task: MIL-011#1
Closes #90

2026-10-13 12:57:42 +08:00

1.7 KiB

Raw Permalink Blame History

Changelog

All notable changes to RepoFoundry. Versions are tags vMAJOR.MINOR.PATCH. The release workflow takes the text of a release page from the entry of its version, so every release needs an entry here before it is started.

Each release lists its changes in these groups, in this order: Breaking, Added, Changed, Fixed. A release with a Breaking entry has a new major version.

python tools/changelog.py check of TirSystem/github-action verifies this file.

[Unreleased]

[0.3.4] - 2026-10-13

Added

Gitea workflows: Quality (shellcheck and shfmt through the shared reusable workflow) and Release (tag and release page from this changelog).
A wiki/ folder with a .publish marker, published to the Gitea wiki by the 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.