[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-20-ports-8080-and-23456-now-explicitly-forbidden-in-sandbox":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KS2GPVYGD722S50GMX93W1ZV","2026-05-20-ports-8080-and-23456-now-explicitly-forbidden-in-sandbox","Breaking","Ports 8080 and 23456 now explicitly forbidden in sandbox expose list","The `not` constraint on sandbox exposed port numbers has been tightened to explicitly exclude ports `8080` and `23456`. Previously, `\"not\": {}` was an empty schema (which never matched anything, effectively a no-op), so any port in the valid range was accepted. Now `\"not\": {\"enum\": [8080, 23456]}` actively rejects those two specific values — clients currently passing `8080` or `23456` in the ports array will receive validation errors.","2026-05-20T11:00:37.968Z"]