3 Commits

Include renames

Author	SHA1	Message	Date
jochen	f2d765320a	gitea forge bundle: name the parent the forge used, match protection rules as the forge does, bound a commit's size and a search's time (issue 539) ... The forge's contents and diffpatch endpoints take a branch, never a commit to build on, so the parent is read from the commit the forge made, and a branch that moved under the commit is said. Blobs are read at the commit read first, not at the branch name. Protection rules match as Gitea 1.27 matches them ([...], {a,b}, escapes, a plain name in any case), in the Go bundle and in guard.ts alike. One commit carries at most 4 MiB per file or patch and 16 MiB together; code search stops at its deadline and says so. The HTTP client the two Go bundles copied is one package, internal/forgehttp.	2026-10-12 12:51:22 +02:00
jochen	10b5e8188a	Refuse a yarn lockfile the scanner stopped in, and a forge answer the cap cut ... Either was read as whole and could leave a pinned version unnamed (review of #128).	2026-10-08 14:52:06 +02:00
jochen	8059f35d17	gitea: say what keeps each npm version and delete only what nothing names (hq ADR 0251) ... Every publish added a version and nothing removed one. A Go bundle beside the TypeScript one keeps what a lockfile or a range on the forge names, what a dist-tag names and the newest five; a dry run unless asked with a why, and nothing deleted while any repository is unread.	2026-10-08 12:00:57 +02:00