diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index afdd80f18d1..30d6297f8da 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -6,7 +6,7 @@ # See https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#permissions. 'permissions': {} 'env': - 'GO_VERSION': '1.26.3' + 'GO_VERSION': '1.26.4' 'NODE_VERSION': '20' 'on': 'push': diff --git a/CHANGELOG.md b/CHANGELOG.md index 6a336b9e3f6..0464aa8d931 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -26,12 +26,16 @@ NOTE: Add new changes BELOW THIS COMMENT. ### Security +- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.26.4][go-1.26.4]. + - The H2C connection establishment via HTTP/1.1 request upgrade is no longer supported. See [RFC 9113][rfc9113]. -- The size of rulelists is limited. This is necessary to prevent a user's machine from becoming overloaded if the filter source misbehaves. +- The size of rulelists is limited. This is necessary to prevent a user's machine from becoming overloaded if the filter source misbehaves. ### Changed +- The interval of filter updates can now be set to any number of ours between 0 and 365 days in the configuration file. + #### Configuration changes - The `filtering` object of the YAML configuration now includes a new property, `max_http_size`, which defines the maximum size of the HTTP request for rulelists. To disable the limitation, set a large size, such as `1 TB`. @@ -40,7 +44,8 @@ NOTE: Add new changes BELOW THIS COMMENT. - Blocked services check on the Custom filtering rules page does not work properly without specifying of a client. -[rfc9113]: https://datatracker.ietf.org/doc/html/rfc9113 +[rfc9113]: https://datatracker.ietf.org/doc/html/rfc9113 +[go-1.26.4]: https://groups.google.com/g/golang-announce/c/tKs3rmcBcKw +## v0.107.78: API changes + +### New `interval` values in `GET /control/filtering/status` and `POST /control/filtering/config` APIs + +The property `interval` of the objects returned from and accepted by the aforementioned APIs can now be any integer between 0 and 8760 (365 days). + ## v0.107.77: API changes ### New `reason` query parameter in 'GET /control/querylog'