Docs/changelog 1.0.4 (#931)

* first draft of changelog

* note the fix

Co-authored-by: Abe Raher <abe@cribl.io>

website/src/pages/docs/changelog.md

@@ -6,6 +6,24 @@ title: Changelog
 
 See the AppScope repo to view [all issues](https://github.com/criblio/appscope/issues).
 
+## AppScope 1.0.4
+
+2022-05-10 - Maintenance Release
+
+Assets are available via Docker and the Cribl CDN at the links below.
+
+- `Docker`: `cribl/scope:1.0.4`
+- `x86`: [https://cdn.cribl.io/dl/scope/1.0.4/linux/x86_64/scope](https://cdn.cribl.io/dl/scope/1.0.4/linux/x86_64/scope)
+- `ARM`: [https://cdn.cribl.io/dl/scope/1.0.4/linux/aarch64/scope](https://cdn.cribl.io/dl/scope/1.0.4/linux/aarch64/scope)
+
+### Fixes
+
+AppScope 1.0.4 aims to resolve reported connectivity issues.
+
+- [#896](https://github.com/criblio/appscope/issues/896) AppScope now creates a connection dedicated to transmitting payload data only if payloads are enabled.
+- [#665](https://github.com/criblio/appscope/issues/665) AppScope now has safeguards to ensure that AppScope does not interfere with scoped processes exiting.
+- [#869](https://github.com/criblio/appscope/issues/869) AppScope now uses an improved algorithm for omitting raw binary data from console events. The improved algorithm is better able to handle commands that switch back and forth between outputting text and outputting raw binary data to the console.
+
 ## AppScope 1.0.3
 
 2022-04-12 - Maintenance Release

website/src/pages/docs/known-issues.md

@@ -10,7 +10,9 @@ title: Known Issues
 
 As of this AppScope release, known issues include:
 
-- [#869](https://github.com/criblio/appscope/issues/869) AppScope's ability to avoid outputting binary data in console messages does not work perfectly in all situations. When data is first sent to the console by a scoped app, AppScope can detect whether it is binary, and if so, redact it while emitting an informative message. But when apps switch back and forth between textual and binary data, AppScope does not detect the change, and binary data can appear in console output.  
+- [#869](https://github.com/criblio/appscope/issues/869) AppScope's ability to avoid outputting binary data in console messages does not work perfectly in all situations. When data is first sent to the console by a scoped app, AppScope can detect whether it is binary, and if so, redact it while emitting an informative message. But when apps switch back and forth between textual and binary data, AppScope does not detect the change, and binary data can appear in console output.
+  - **Fix:** 1.0.4
+
 - [#831](https://github.com/criblio/appscope/issues/831) When you scope the Microsoft Edge browser, AppScope fails to collect some HTTP events in these situations: (1) When Edge requests the use of HTTP/3; (2) When Edge uses HTTP/1.1 over UDP to request a list of plug-and-play devices from a Microsoft service; and, (3) when Edge uses SSL.  
 
 ## AppScope 1.0.0