Release v3.1.16 (#6649)

Co-authored-by: gaichao168 <1432681790@qq.com>
Co-authored-by: 10966 <gaichaowang@addcn.com>
Co-authored-by: kingIZZZY <logic.cpp@gmail.com>
Co-authored-by: guandeng <guandeng@Hotmail.com>

.github/ISSUE_TEMPLATE/---support-question.md

@@ -7,8 +7,8 @@ assignees: ''
 
 ---
 
-## Before you submit this issue, you has been search all existed issues and search the [documentation](https://hyperf.wiki)
-- [] I've been search all existed issues
-- [] I've been read all documentation
+## Before you submit an issue, please be sure to search through existing issues as well as search through the [documentation](https://hyperf.wiki)
+- [] I've searched all existing issues
+- [] I've read all relevant documentation I could find
 
 ### Describe your question

CHANGELOG-3.1.md

@@ -1,5 +1,6 @@
-# v3.1.16 - TBD
+# v3.1.17 - TBD
 
+# v3.1.16 - 2024-04-02
 
 ## Added
 

docs/en/awesome-components.md

@@ -49,7 +49,7 @@ We have provided you with a [Hyperf component development guide](en/component-gu
 ## Database
 
 - [hyperf/database](https://github.com/hyperf/database) Based on the Eloquent database ORM forked by Hyperf, this component can be reused in other frameworks
-- [hyperf/model-cache](https://github.com/hyperf/model-cache) [Hyperf/database](https://github.com/hyperf/database) component-based automatic model caching component provided by Hyperf officially
+- [hyperf/model-cache](https://github.com/hyperf/model-cache) [hyperf/database](https://github.com/hyperf/database) component-based automatic model caching component provided by Hyperf officially
 
 ## Dependency injection container
 

docs/en/changelog/3.1.md

@@ -1,5 +1,21 @@
 # Changelogs
 
+# v3.1.16 - 2024-04-02
+
+## Added
+
+- [#6632](https://github.com/hyperf/hyperf/pull/6632) Support to set headers for `websocket-client`.
+- [#6648](https://github.com/hyperf/hyperf/pull/6648) Return result about websocket sender`push``disconnect`.
+
+## Fixed
+
+- [#6633](https://github.com/hyperf/hyperf/pull/6633) Fixed bug that crontab will be skipped sometimes.
+- [#6635](https://github.com/hyperf/hyperf/pull/6635) Fixed AMQP `ConsumerMessage::getQueue` return type.
+
+## Optimized
+
+- [#6640](https://github.com/hyperf/hyperf/pull/6640) Support PHP8 Attribute for `hyperf/constants`.
+
 # v3.1.15 - 2024-03-28
 
 ## Added

docs/en/component-guide/configprovider.md

@@ -97,7 +97,7 @@ The configuration of `ConfigProvider` is not necessarily divided in this way. Th
 Since the `extra` attribute in `composer.json` has no other effect and influence when the data is not used, the definitions in these components will not cause any interference and influence when used by other frameworks, so `ConfigProvider` is A mechanism that only works on the Hyperf framework, and will not have any impact on other frameworks that do not use this mechanism, which lays the foundation for component reuse, but it also requires that the following must be followed when designing components specification:
 
 - All classes must be designed to allow standard `OOP` usage, and all Hyperf-specific features must be provided as enhancements and in separate classes, which means they can still be used in non-Hyperf frameworks through standard means to realize the use of components;
-- If the dependency design of the component can meet the [PSR standard](https://www.php-fig.org/psr), it will be satisfied first and depend on the corresponding interface instead of the implementation class; such as [PSR standard](https:// www.php-fig.org/psr) does not contain functions, then it can satisfy the interface in the contract library [Hyperf/contract](https://github.com/hyperf/contract) defined by Hyperf, which is satisfied first and depends on The corresponding interface rather than the implementation class;
+- If the dependency design of the component can meet the [PSR standard](https://www.php-fig.org/psr), it will be satisfied first and depend on the corresponding interface instead of the implementation class; such as [PSR standard](https:// www.php-fig.org/psr) does not contain functions, then it can satisfy the interface in the contract library [hyperf/contract](https://github.com/hyperf/contract) defined by Hyperf, which is satisfied first and depends on The corresponding interface rather than the implementation class;
 - For the enhanced function classes added to implement Hyperf's proprietary functions, generally speaking, they also have dependencies on some components of Hyperf, so the dependencies of these components should not be written in the `require` item of `composer.json`, but write exists as a suggestion in the `suggest` item;
 - Component design should not perform any dependency injection through annotations, and the injection method should only use `constructor injection`, which can also meet the use under `OOP`;
 - Component design should not define any functions through annotations, and function definitions should only be defined through `ConfigProvider`;

docs/en/filesystem.md

@@ -201,7 +201,7 @@ class IndexController
 
 If you want to access files uploaded locally via http, please add the following configuration to the `config/autoload/server.php` configuration.
 
-```
+```php
 return [
     'settings' => [
         ...

docs/en/quick-start/install.md

@@ -4,7 +4,7 @@
 
 Hyperf can only run on the Linux and MacOS system environments. However, due to the development of Docker virtualization technology, it is possible to use Windows as the system environment using Docker for Windows. If you use MacOS we recommend a local deployment to avoid the Docker shared disk causing slow startup times for Hyperf.
 
-Various Dockerfiles have been prepared for in the [hyperf/hyperf-docker](https://github.com/hyperf/hyperf-docker) project, or you can use a prebuilt image based on [hyperf\Hyperf](https://hub.docker.com/r/hyperf/hyperf).
+Various Dockerfiles have been prepared for in the [hyperf/hyperf-docker](https://github.com/hyperf/hyperf-docker) project, or you can use a prebuilt image based on [hyperf/hyperf](https://hub.docker.com/r/hyperf/hyperf).
 
 If you don't use Docker as the basis for your system environment, you can also consider using [Box](en/eco/box.md) as the basic environment for running. If you wish to set up the environment yourself, you need to make sure that your native environment meets the following requirements: