{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":563434928,"defaultBranch":"main","name":"fetch","ownerLogin":"wintercg","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2022-11-08T15:53:31.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/102753901?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1692361704.0","currentOid":""},"activityList":{"items":[{"before":"176169ee58dfb325833211bf67edfc66e6aa4bf6","after":null,"ref":"refs/heads/fix-ci","pushedAt":"2023-08-18T12:28:24.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"}},{"before":"8f994ff499359e381cc9e6b1403b18e7b83840e4","after":"adc1629cd9aecc525e6391c903fae3c2eed46f67","ref":"refs/heads/main","pushedAt":"2023-08-18T12:28:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"[ci] Make deploys fail if the spec build fails (#21)\n\nOur CI deploy action currently asks a server at api.csswg.org to build\r\nthe spec, and then uses the response to that request as the build\r\noutput. However, it does not check that the response's HTTP status\r\ncode is successful, which can result in Internal Server Errors in that\r\nserver being \"propagated\" to this spec, rather than resulting in a\r\nfailed build. Similarly, fatal errors in building the spec (for\r\ninvalid Bikeshed syntax, for example) would result in the list of\r\nerrors being deployed.\r\n\r\nThis PR fixes that by allowing `curl` to fail for non-successful HTTP\r\nstatus codes.","shortMessageHtmlLink":"[ci] Make deploys fail if the spec build fails (#21)"}},{"before":"2d2857caa2e07ce3e765ed5263812b99e20628f5","after":"176169ee58dfb325833211bf67edfc66e6aa4bf6","ref":"refs/heads/fix-ci","pushedAt":"2023-08-17T10:26:58.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Revert \"Test: should result in a build error\"\n\nThis reverts commit 2d2857caa2e07ce3e765ed5263812b99e20628f5.","shortMessageHtmlLink":"Revert \"Test: should result in a build error\""}},{"before":"db74dcc3391eb612f8abdfeec29d952a52805afe","after":"2d2857caa2e07ce3e765ed5263812b99e20628f5","ref":"refs/heads/fix-ci","pushedAt":"2023-08-17T10:26:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Test: should result in a build error","shortMessageHtmlLink":"Test: should result in a build error"}},{"before":null,"after":"db74dcc3391eb612f8abdfeec29d952a52805afe","ref":"refs/heads/fix-ci","pushedAt":"2023-08-17T10:23:46.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"[ci] Make deploys fail if the spec build fails\n\nOur CI deploy action currently asks a server at api.csswg.org to build\nthe spec, and then uses the response to that request as the build\noutput. However, it does not check that the response's HTTP status\ncode is successful, which can result in Internal Server Errors in that\nserver being \"propagated\" to this spec, rather than resulting in a\nfailed build. Similarly, fatal errors in building the spec (for\ninvalid Bikeshed syntax, for example) would result in the list of\nerrors being deployed.\n\nThis PR fixes that by allowing `curl` to fail for non-successful HTTP\nstatus codes.","shortMessageHtmlLink":"[ci] Make deploys fail if the spec build fails"}},{"before":"db74dcc3391eb612f8abdfeec29d952a52805afe","after":null,"ref":"refs/heads/fix-ci","pushedAt":"2023-08-17T10:22:56.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"}},{"before":null,"after":"db74dcc3391eb612f8abdfeec29d952a52805afe","ref":"refs/heads/fix-ci","pushedAt":"2023-08-17T10:21:30.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"[ci] Make deploys fail if the spec build fails\n\nOur CI deploy action currently asks a server at api.csswg.org to build\nthe spec, and then uses the response to that request as the build\noutput. However, it does not check that the response's HTTP status\ncode is successful, which can result in Internal Server Errors in that\nserver being \"propagated\" to this spec, rather than resulting in a\nfailed build. Similarly, fatal errors in building the spec (for\ninvalid Bikeshed syntax, for example) would result in the list of\nerrors being deployed.\n\nThis PR fixes that by allowing `curl` to fail for non-successful HTTP\nstatus codes.","shortMessageHtmlLink":"[ci] Make deploys fail if the spec build fails"}},{"before":"ba7f43946186d50f86e9dbc2400b1afb9d33a49e","after":null,"ref":"refs/heads/header-filtering","pushedAt":"2023-08-16T21:22:48.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Ethan-Arrowood","name":"Ethan Arrowood","path":"/Ethan-Arrowood","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16144158?s=80&v=4"}},{"before":"bbb32faa2320d86d4c83fc2ad12fc1162b90d41b","after":"8f994ff499359e381cc9e6b1403b18e7b83840e4","ref":"refs/heads/main","pushedAt":"2023-08-16T21:22:44.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"Ethan-Arrowood","name":"Ethan Arrowood","path":"/Ethan-Arrowood","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16144158?s=80&v=4"},"commit":{"message":"Relax forbidden header restrictions for non-browser runtimes (#19)\n\n* Relax forbidden header restrictions for non-browser runtimes\r\n\r\nWeb browsers treat certain request and response headers as forbidden\r\n–forbidden request headers are impossible to set in requests, and\r\nforbidden response headers are always filtered off of even basic\r\nfiltered response (i.e. responses for same-origin fetches).\r\n\r\nWhile some of these forbidden request headers make sense generally\r\n(for example, `Date`, `Host`, `Transfer-Encoding`), others don't make\r\nsense for implementers that don't support CORS or cookies. And the\r\nonly forbidden response headers (`Set-Cookie` and `Set-Cookie2`) only\r\nmake sense for implementers that support cookies.\r\n\r\nTo allow different kinds of implementers with different requirements,\r\nthis change adds a \"conformance classes\" section defining support for\r\nCORS and cookies. It then changes the definitions of forbidden request\r\nand response headers to depend on the user agent's conformance\r\nclasses.\r\n\r\n* Update fetch.bs\r\n\r\nCo-authored-by: Ethan Arrowood \r\n\r\n* Update fetch.bs\r\n\r\nCo-authored-by: Ethan Arrowood \r\n\r\n---------\r\n\r\nCo-authored-by: Ethan Arrowood ","shortMessageHtmlLink":"Relax forbidden header restrictions for non-browser runtimes (#19)"}},{"before":"ea86e9f6ed7595d202c865f8956b695b3886fc99","after":"ba7f43946186d50f86e9dbc2400b1afb9d33a49e","ref":"refs/heads/header-filtering","pushedAt":"2023-07-06T14:27:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Update fetch.bs\n\nCo-authored-by: Ethan Arrowood ","shortMessageHtmlLink":"Update fetch.bs"}},{"before":"28ba87c5a3e1f67015a6ac48c5b0cbb455d6b9b9","after":"ea86e9f6ed7595d202c865f8956b695b3886fc99","ref":"refs/heads/header-filtering","pushedAt":"2023-07-06T14:27:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Update fetch.bs\n\nCo-authored-by: Ethan Arrowood ","shortMessageHtmlLink":"Update fetch.bs"}},{"before":"6459a0bc3d2568db6fcdec540b4918d9b6a3ae48","after":"bbb32faa2320d86d4c83fc2ad12fc1162b90d41b","ref":"refs/heads/main","pushedAt":"2023-04-17T22:32:37.047Z","pushType":"push","commitsCount":16,"pusher":{"login":"Ethan-Arrowood","name":"Ethan Arrowood","path":"/Ethan-Arrowood","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16144158?s=80&v=4"},"commit":{"message":"Merge branch 'whatwg:main' into main","shortMessageHtmlLink":"Merge branch 'whatwg:main' into main"}},{"before":"38d30b3563fa58a6a2bd78b401f5409881d5d006","after":null,"ref":"refs/heads/whatwg-box-styling","pushedAt":"2023-03-09T20:03:57.747Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"}},{"before":"f51fea83f251dd98173c4e1e943bccf6a699b2bf","after":"6459a0bc3d2568db6fcdec540b4918d9b6a3ae48","ref":"refs/heads/main","pushedAt":"2023-03-09T20:00:51.475Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"Ethan-Arrowood","name":"Ethan Arrowood","path":"/Ethan-Arrowood","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16144158?s=80&v=4"},"commit":{"message":"Add missing styles for some of the notes (#17)\n\nWHATWG specs, including the Fetch spec, use a stylesheet different\r\nfrom the W3C default which WinterCG uses. This WHATWG stylesheet\r\nsupports various types of notes and boxes with specific classes that\r\nare not supported in the W3C default stylesheet.\r\n\r\nThis change adds styling for these classes, giving them a style\r\nconsistent with that of various types of notes in the W3C stylesheet.","shortMessageHtmlLink":"Add missing styles for some of the notes (#17)"}},{"before":"eff17d171e59279c3e699fcfc482c4349fe07b21","after":"38d30b3563fa58a6a2bd78b401f5409881d5d006","ref":"refs/heads/whatwg-box-styling","pushedAt":"2023-03-07T17:23:30.495Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Add missing styles for some of the notes\n\nWHATWG specs, including the Fetch spec, use a stylesheet different\nfrom the W3C default which WinterCG uses. This WHATWG stylesheet\nsupports various types of notes and boxes with specific classes that\nare not supported in the W3C default stylesheet.\n\nThis change adds styling for these classes, giving them a style\nconsistent with that of various types of notes in the W3C stylesheet.","shortMessageHtmlLink":"Add missing styles for some of the notes"}},{"before":"b409f803e00c144c6c81cce1e1c88e8784b32c66","after":"28ba87c5a3e1f67015a6ac48c5b0cbb455d6b9b9","ref":"refs/heads/header-filtering","pushedAt":"2023-03-07T17:20:17.709Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Relax forbidden header restrictions for non-browser runtimes\n\nWeb browsers treat certain request and response headers as forbidden\n–forbidden request headers are impossible to set in requests, and\nforbidden response headers are always filtered off of even basic\nfiltered response (i.e. responses for same-origin fetches).\n\nWhile some of these forbidden request headers make sense generally\n(for example, `Date`, `Host`, `Transfer-Encoding`), others don't make\nsense for implementers that don't support CORS or cookies. And the\nonly forbidden response headers (`Set-Cookie` and `Set-Cookie2`) only\nmake sense for implementers that support cookies.\n\nTo allow different kinds of implementers with different requirements,\nthis change adds a \"conformance classes\" section defining support for\nCORS and cookies. It then changes the definitions of forbidden request\nand response headers to depend on the user agent's conformance\nclasses.","shortMessageHtmlLink":"Relax forbidden header restrictions for non-browser runtimes"}},{"before":"3573a86b83b23425cc622a10492bad7333095e0e","after":"b409f803e00c144c6c81cce1e1c88e8784b32c66","ref":"refs/heads/header-filtering","pushedAt":"2023-03-07T16:33:57.009Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Relax forbidden header restrictions for non-browser runtimes","shortMessageHtmlLink":"Relax forbidden header restrictions for non-browser runtimes"}},{"before":null,"after":"3573a86b83b23425cc622a10492bad7333095e0e","ref":"refs/heads/header-filtering","pushedAt":"2023-03-07T16:32:55.411Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"andreubotella","name":"Andreu Botella","path":"/andreubotella","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8225977?s=80&v=4"},"commit":{"message":"Relax forbidden header restrictions for non-browser runtimes","shortMessageHtmlLink":"Relax forbidden header restrictions for non-browser runtimes"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADbYsBGwA","startCursor":null,"endCursor":null}},"title":"Activity · wintercg/fetch"}