Merge branch 'release/4.1.1' into 'develop'

chore(release): Added release notes and changelog for 4.1.1

See merge request passbolt/passbolt_docker!218

Author: dlen

CHANGELOG.md

@@ -3,8 +3,23 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 
-## [Unreleased](https://github.com/passbolt/passbolt_docker/compare/4.1.0...HEAD)
-- Add EMAIL_TRANSPORT_DEFAULT_PASSWORD and EMAIL_TRANSPORT_DEFAULT_PASSWORD to docker secrets. 
+## [Unreleased](https://github.com/passbolt/passbolt_docker/compare/4.1.1...HEAD)
+
+## [4.1.1](https://github.com/passbolt/passbolt_docker/compare/4.1.0...4.1.1) - 2025-04-02
+
+### Added
+
+- Support EMAIL_TRANSPORT_DEFAULT_PASSWORD and EMAIL_TRANSPORT_DEFAULT_PASSWORD to docker secrets.
+
+### Fixed
+
+- Readme requirements no longer contain rng/tools or haveged mentions. Kernels newer than 5.12 should not require such tools for entropy generation
+- Readme instructions for non-root first user creation added
+- Readme PASSBOLT_SSL_FORCE default value updated to false
+
+### Changed
+
+- Entrypoint no longer checks for entropy_avail size. Fixes #229
 
 ## [4.1.0](https://github.com/passbolt/passbolt_docker/compare/4.0.0...4.1.0) - 2024-12-30
 

RELEASE_NOTES.md

@@ -1,4 +1,8 @@
-Announcing the immediate availability of passbolt's docker image 4.1.0.
+Announcing the immediate availability of passbolt's docker repository 4.1.1.
 
-This is a minor change that fixes a logging issue where 500 errors were not redirected to standard output.
-Also, it fixes issues on image testing and added the release notes automation on GitHub.
+This release adds docker secrets support for EMAIL_TRANSPORT_DEFAULT_PASSWORD
+and EMAIL_TRANSPORT_DEFAULT_USERNAME environment variables thanks to @Shtiggs
+
+It also includes a warning message when APP_FULL_BASE_URL environment variable
+is not set to mitigate host header injection attacks. You can obtain more
+information about the subject in the following link: <https://owasp.org/www-project-web-security-testing-guide/v42/4-Web_Application_Security_Testing/07-Input_Validation_Testing/17-Testing_for_Host_Header_Injection>