fix(mcp): allowedorigins-removed message says v1.3.0, not v2.0.0
This commit is contained in:
@@ -29,12 +29,12 @@ func init() {
|
||||
// checkAllowedOriginsRemoved flags any reference to the removed
|
||||
// web.Config.AllowedOrigins field — both a selector (cfg.Web.AllowedOrigins) and a
|
||||
// struct-literal key (web.Config{AllowedOrigins: ...}). It was env-backed through
|
||||
// v1.1.x, became a code-only override in v1.2.0, and was removed in v2.0.0. Code
|
||||
// that still reads it compiled but silently served no CORS in v1.2.0; in v2.0.0 it
|
||||
// v1.1.x, became a code-only override in v1.2.0, and was removed in v1.3.0. Code
|
||||
// that still reads it compiled but silently served no CORS in v1.2.0; in v1.3.0 it
|
||||
// no longer compiles. CORS now lives solely on server.Config.CORSOrigins.
|
||||
func checkAllowedOriginsRemoved(c *Context) []Finding {
|
||||
const (
|
||||
msg = "web.Config.AllowedOrigins was removed in v2.0.0 — CORS lives on Server.CORSOrigins (env EINHERJAR_SERVER_CORS_ORIGINS)"
|
||||
msg = "web.Config.AllowedOrigins was removed in v1.3.0 — CORS lives on Server.CORSOrigins (env EINHERJAR_SERVER_CORS_ORIGINS)"
|
||||
hint = "Read cfg.Server.CORSOrigins (or set it in code); web.New applies it automatically. Never reintroduce a field/var for CORS origins."
|
||||
)
|
||||
seen := map[int]bool{}
|
||||
|
||||
Reference in New Issue
Block a user