From 5bf2f57f537f07e745ef9c917248fecb563d8cd5 Mon Sep 17 00:00:00 2001 From: Jonathan Miller Date: Sat, 30 May 2026 11:06:40 -0500 Subject: [PATCH] docs: update CHANGELOG for actions bot rebrand and deploy trigger Co-Authored-By: Claude Opus 4.6 (1M context) --- CHANGELOG.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index a493f375ae..14775b25ed 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,23 @@ This changelog goes through the changes that have been made in each release without substantial changes to our git log; to see the highlights of what has been added to each release, please refer to the [blog](https://blog.gitea.com). +## [v1.26.1-moko.05.06.00] - 2026-05-30 + +* FEATURES + * feat(actions): rebrand actions bot user to mokogitea-actions (#233, #234) + * Name: gitea-actions → mokogitea-actions, FullName: MokoGitea Actions + * Email: mokogitea-actions[bot]@mokoconsulting.tech + * Backward-compatible: recognizes github-actions[bot], gitea-actions[bot], mokogitea-actions[bot] + * feat(actions): add actions bot user to branch protection whitelist (#233, #234) + * New toggles: WhitelistActionsUser, MergeWhitelistActionsUser, ForcePushAllowlistActionsUser + * Allows CI/CD workflows to push/merge/force-push to protected branches when enabled + * DB migration v334 adds the three boolean columns + * Exposed in API (create/edit branch protection) and web UI settings +* INFRASTRUCTURE + * fix(ci): auto-deploy to production on merge to main (#235) + * Deploy workflow now triggers on push to main, not just manual dispatch + * Version derived from git describe for auto-deploys + ## [v1.26.1-moko.04.00.00] - 2026-05-24 * SECURITY