Gusted 533c87da65 [GITEA] Make HTTPS schema default for Swagger ... - Switch the supported schemas for the Swagger API around, such that https is the first one listed. This ensures that when the Swagger API is used it will default to the https schema, which is likely the schema you want to use in the majority of the cases. - Resolves #1895 BREAKING CHANGE NOTICE: If you are using the Swagger API JSON directly to communicate with the Forgejo API, the library you are using may be using the first schema defined in the JSON file (e.g. https://code.forgejo.org/swagger.v1.json) to construct the request url, this used to be `http` but has now changed to `https`. This can cause failures if you want to send the swagger request over `http` (and there is no HTTPS redirection configured). (cherry picked from commit 81e5f43886) (cherry picked from commit d847469ea2) (cherry picked from commit 96e75e1d5c) (cherry picked from commit 65baa64261) (cherry picked from commit cd3e0a74e6) (cherry picked from commit a3127e90b2) (cherry picked from commit 2b22272dc5) (cherry picked from commit 7363790592) (cherry picked from commit 432b9a4451)		2024-02-05 16:09:41 +01:00
..
actions	Add artifacts v4 jwt to job message and accept it (#28885)	2024-02-02 14:25:59 +00:00
forgejo/v1	[CLEANUP] Reuse ForgejoVersion variable	2024-02-05 14:45:11 +01:00
packages	[GITEA] Drop sha256-simd in favor of stdlib	2024-02-05 16:09:40 +01:00
v1	[GITEA] Make HTTPS schema default for Swagger	2024-02-05 16:09:41 +01:00