5 Commits

Include renames

Author	SHA1	Message	Date
JonKazama-Hellion	5771573a94	fix(ci): keep bilingual forge-announce embeds from merging ... Both the DE and EN embed carried the same release url, which makes Discord merge url-identical embeds and render only the first embed's description. The EN block was posted and stored but never shown, so every auto-announce from v1.4.6 onward displayed German only. Drop the url from the EN embed so Discord stacks both as separate cards with both descriptions visible.	2026-05-22 09:56:17 +02:00
JonKazama-Hellion	0220e5d756	chore(linting): refresh configs and sweep auto-fix ... Pull in the refreshed linter and tooling configs (editorconfig, gitignore, gitattributes, prettierignore, prettierrc, markdownlint, yamllint, env.example, dotnet-tools) and run prettier and markdownlint in --fix / --write mode across the repo so the existing tree matches the new rules. - prettier 2-space indent on yaml/yml and json overrides, asterisk strong, underscore emphasis, proseWrap always - markdownlint MD007 indent aligned to 2 and MD049 to underscore so prettier output stays passing - preflight Block F also ignores CLAUDE.md (gitignored personal file) - prettierignore extended to keep HellionChat.yaml manifest and the NuGet packages.lock.json out of the formatter No semantic content changed; csharpier, build, full build-suite (729/729) and the new prettier/markdownlint/yamllint checks all green.	2026-05-17 17:20:55 +02:00
JonKazama-Hellion	94e4828aeb	fix: update forge-announce.yml to use the correct branch	2026-05-12 22:33:53 +02:00
JonKazama-Hellion	612bf8814f	fix(ci): match release + forge-announce parsing to current yaml format ... Both workflows looked for "**Hellion Chat <version>" as the changelog subblock header, but the yaml convention is "**v<version> — <subtitle>" (matches verify-changelog-sync.sh and the slim-rule grep). Plus the indent-strip was 2 spaces, but prettier writes the changelog block with 4-space indent. Both regressions silently failed every release-workflow run since the format change — likely why v1.4.3 was released manually. Sync header marker to "**v$version " and indent-strip to 4 spaces in both files.	2026-05-12 11:17:41 +02:00
JonKazama-Hellion	be17472cd5	chore(ci): migrate workflows to .gitea/workflows/ ... Gitea Actions reads exclusively from .gitea/workflows/, not from .github/workflows/. Since the cutover in v1.4.3 only the security workflow has been running — release and forge-announce silently sat in the wrong directory and never fired on any tag push. v1.4.3 must have been released manually. Move build, release and forge-announce yamls to .gitea/workflows/. The .github/forge-posts/ and .github/release-footer.md data files stay where they are; the workflows reference them by repo-relative path and that keeps working. For the v1.4.4 backfill: workflow_dispatch via the Gitea web UI with tag=v1.4.4 will run release.yml + forge-announce.yml against the tagged tree (which doesn't contain this migration). The dispatch yaml itself is read from the default branch, not the tag, so the missing yamls in the v1.4.4 tag tree don't matter.	2026-05-12 11:05:52 +02:00