[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-06-22-icon-field-now-restricted-to-sha-1-hash-only-https-urls-no":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},"01KVRS0RQKM05NZH6SVTB8NKGP","2026-06-22-icon-field-now-restricted-to-sha-1-hash-only-https-urls-no","Breaking","icon field now restricted to SHA-1 hash only; https:\u002F\u002F URLs no longer accepted","The **`icon`** field previously accepted either a SHA-1 hash or an `https:\u002F\u002F` URL; it now only accepts a 40-character hex SHA-1 hash (enforced by `pattern: ^[0-9a-fA-F]{40}$`). Clients currently supplying an `https:\u002F\u002F` URL for the branding icon will fail validation with this updated spec, making this a breaking change for those integrations.","2026-06-22T23:00:32.115Z"]