Files
HellionChat/.github/PULL_REQUEST_TEMPLATE.md
JonKazama-Hellion e594258cf3
Build / Build (Release) (push) Successful in 41s
Release / Build and attach release ZIP (push) Successful in 2m4s
Forge Announce / Post changelog to Hellion Forge (push) Successful in 11s
Migrate residual URLs and security-report path to Forge
Cleanup pass after the v1.4.3 cutover. Five files still carried
gitea.com hosts or dead github.com security-advisory links because
they were not touched in the prior URL sweep.

- forge-announce.yml: Discord embed avatar and tag link
- release-footer.md: custom-repo URL plus six doc/license links
- bug_report.yml, config.yml, PULL_REQUEST_TEMPLATE.md: replace
  github.com/.../security/advisories/new with mailto:kontakt@
  hellion-media.de. Gitea has no privately-reportable advisory
  feature; e-mail is the closest functional equivalent.

Pure string replacement, no logic change.
2026-05-09 08:39:19 +02:00

2.2 KiB

Summary

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds behaviour)
  • Breaking change (config migration, removed feature, or behaviour change that user-visible defaults rely on)
  • Documentation only
  • Translation update
  • Build, CI or tooling change

Linked issue

How I tested this

User-visible changes

Compatibility notes

Checklist

  • I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md.
  • My change matches the existing code style (.editorconfig).
  • I added or updated tests where the existing test infrastructure made that practical, or I have explained why tests are not applicable.
  • I updated the README, in-plugin strings or documentation if my change is user-visible.
  • I did not include any AI-generated code without disclosing it in the PR description (see AI_DISCLOSURE.md).
  • I confirm my contribution is released under the EUPL-1.2.