3 Commits

Include renames

Author	SHA1	Message	Date
wxiaoguangandsilverwind	d919301d36	refactor: remove UnmarshalHandleDoubleEncode patch and fix repo unit TODO (#39998) ... Remove the `UnmarshalHandleDoubleEncode` runtime workaround for an old xorm bug, and normalize legacy double-encoded JSON in `repo_unit.config` and `login_source.cfg` with a migration instead. - Config `FromDB` no longer fails on corrupted values. A broken auth source is deactivated, so admins can still fix it in the admin panel - Remove `ProjectsConfig.GetProjectsMode`, `FromDB` already defaults `ProjectsMode` Actually it doesn't need so many changes, just because AI thinks it should handle "corrupted database value" for auth sources. --------- Signed-off-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: silverwind <me@silverwind.io>	2026-11-04 05:28:49 +00:00
3 people	151ef80e28	use experimental go json v2 library (#35392) ... details: https://pkg.go.dev/encoding/json/v2 --------- Co-authored-by: techknowlogick <matti@mdranta.net> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2025-09-28 08:03:36 +00:00
wxiaoguang	51d86adb6d	Fix some migration and repo name problems (#33986) ... 1. Ignore empty inputs in `UnmarshalHandleDoubleEncode` 2. Ignore non-existing `stateEvent.User` in gitlab migration 3. Enable `release` and `wiki` units when they are selected in migration 4. Sanitize repo name for migration and new repo	2025-03-24 20:26:58 -07:00