v4.25.0

[TheTrunk]

• Improvements in syncthing;
• Packages updates;
• Corrects netcat installation;
• Improvements on marketplace;
• Only run checkMyAppsAvailability checks when daemon is synced;
• Improvements in docker prune;
• Improvements on application install checks so an App is not installed on new instances when it is already running on the defined number of instances.
• New Master/Slave Solution for decentralized persistent data container. With this new solution, the app will be only running on one instance (the master) and the others will be stopped (slaves), syncing the container data, and checking if master is down, when it is down, the slave start so one will be designated the new master. To use the new feature prepend g: to your container data on application specifications. There were also changes done on Flux Domain Manager (FDM) for this solution. You can read more about this new feature here: https://docs.google.com/document/d/10qGstnJnCqthTWvTsTnB--LKwC1e_HJTQv6l70l0T3Q/edit?usp=sharing

This version will be enforced on January 23th.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ab1a1e8) 51.19% compared to head (44a89a0) 50.67%.
Report is 30 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1182      +/-   ##
==========================================
- Coverage   51.19%   50.67%   -0.53%     
==========================================
  Files          43       43              
  Lines       13936    14101     +165     
==========================================
+ Hits         7134     7145      +11     
- Misses       6802     6956     +154     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
8398280	PGP Private Key	9479e36	HomeUI/dist/js/index.js	View secret
8398280	PGP Private Key	9479e36	HomeUI/dist/js/index.js	View secret
8398280	PGP Private Key	e04bee7	HomeUI/dist/js/index.js	View secret
8398280	PGP Private Key	e04bee7	HomeUI/dist/js/index.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[Cabecinha84]

Ack