This package was added during the resolution of issues with Boards CI tests. This pull request isolates and tests the package's impact after recent npm changes. It was found that removing the stub package did not result in any issues.
This will be shown in the system console to let users know
which search backend is active.
Implemented via adding an extra param in the ping response.
https://mattermost.atlassian.net/browse/MM-49984
```release-note
The database section in the system console now has an additional
read-only section which shows the active search backend in use.
This can be helpful to confirm which is the currently active
search engine when there are multiple of them configured.
```
---------
Co-authored-by: Mattermost Build <build@mattermost.com>
We would return "nil, nil" if a plugin was on the blocklist.
This would cause a nil dereference panic while trying to add
struct fields from manifest to the audit logs.
To avoid it, we return an error explicitly and ignore the
error ids to unnecessarily have it log an error.
https://mattermost.atlassian.net/browse/MM-51786
```release-note
NONE
```
* Enforce minimum 10 seats in seats selector
* Ensure initial value is validated as well
* Fix linter
* fix tests
* Add a test for 10 seat minimum
* Fix linter, merge master
* Enforce minimum 10 seats in seats selector
* Ensure initial value is validated as well
* Fix linter
* fix tests
* Add a test for 10 seat minimum
* Fix linter, merge master
* Enforce minimum 10 seats in seats selector
* Ensure initial value is validated as well
* Fix linter
* fix tests
* Add a test for 10 seat minimum
* Fix linter, merge master
After the monorepo integration, the boards product
was started before we started the hub.
This led to a data race where the GetHubForUserId was actually
called before the hub was initialized.
To fix this we initialize the platform first, and then the products.
https://mattermost.atlassian.net/browse/MM-52009
```release-note
NONE
```
"global-styles" was added to hoist fewer dependencies from packages to the root node_modules and was initially intended to fix some issues with mismatched dependency versions in the Boards unit tests. However, it was found to be causing problems when the same version of dependencies was used across the products.
* License public key to test env for mono-repo
* Fix error modal showing on a successful trial request
* Adjustments for new banners
* stashing
* Undo accidental merge
* fixes
* clean up dev stuff, fix style
* Adjust padding on announcement bar button
---------
Co-authored-by: Mattermost Build <build@mattermost.com>
* [MM-51412] - In-product banner to communicate Cloud Free deprecation
* fix lint
* make improvements
* make improvements
* put banners behind feature flag
* cloud free overage case
* add unit tests
* feedback impl
* fix test
* rename and enable feature flag by default
* fix alert banner mode
* read end date from env var
* disable ff by default
* enter cloud free deprecation date
* remove env var
* fix text
---------
Co-authored-by: Mattermost Build <build@mattermost.com>
* Do not shutdown DB handle from boards product
```
warn [2023-04-12 09:16:55.397 +05:30] Failed to save status caller="platform/status.go:175" user_id=gt5aricnu7g7xkr4jstfybgmbc error="failed to upsert Status: sql: database is closed"
```
The DB handle is a global object that is finally closed
at a higher layer after all the necessary tasks are finished.
So closing it prematurely, in the boards shutdown phase
is not necessary and can cause failures as observed above.
To fix this, we just remove the shutdown method.
```release-note
NONE
```
* fix tests
```release-note
NONE
```
The version in package.json was added to display the workspace name in the terminal for playbooks. Additionally, it was ensured that all products now have the same version number, as the release of all products is tied to a single release channel.
We are defining the workflow directive to for `Artifacts generation and upload`/cd/Download artifacts step.
To be the workflow_id from the calling workflow
Signed-off-by: Akis Maziotis <akis.maziotis@mattermost.com>
Mockery started to throw errors like "Unexpected package creation during export data loading".
This was consistently reproducible locally and on upgrade, it has gone away.
```release-note
NONE
```
