Bump docker tags

[leonardocustodio]

PR Type

enhancement, configuration changes

---

Description

• Updated Docker image tags for the app, websocket, ingest, relay, and beam services from v1.9.0 to v1.10.0.
• Updated the Docker image tag for the platform-decoder service to v1.9.1.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	docker-compose.yml Update Docker image tags to newer versions                              docker-compose.yml Updated Docker image tags for multiple services from v1.9.0 to v1.10.0 Ensured consistency across services by updating the platform-decoder image to v1.9.1 +5/-5

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Ensure consistent versioning across all services using the same base image Ensure that the version bump in the Docker image tag is consistent across all services that use the same base image. This helps in maintaining consistency and avoiding potential issues due to version mismatches between interdependent services. docker-compose.yml [37] +image: enjin/platform:v1.10.0 - Suggestion importance[1-10]: 8 Why: This suggestion is valid and important for maintaining consistency across services, which can prevent potential issues due to version mismatches. The suggestion is correctly derived from the PR code diff.	8
Possible issue	Verify the availability of the new Docker image version in the registry Verify that the updated version of the Docker image (enjin/platform:v1.10.0) is available and correctly tagged in your Docker registry before deploying. This prevents runtime errors due to non-existent Docker images. docker-compose.yml [37] +image: enjin/platform:v1.10.0 - Suggestion importance[1-10]: 7 Why: This is a good practice to avoid runtime errors due to non-existent Docker images. It is a valid suggestion but more of a procedural check rather than a code change.	7
Enhancement	Add health checks for services using the new Docker image version Ensure that all Docker services have appropriate health checks configured, especially when updating to a new version like enjin/platform:v1.10.0. This can help in quickly identifying and resolving issues that might arise from the new deployment. docker-compose.yml [37] +image: enjin/platform:v1.10.0 - Suggestion importance[1-10]: 7 Why: Adding health checks is a good enhancement to ensure the stability of services after updating the Docker image. This suggestion is valid and derived from the PR code diff.	7
Maintainability	Implement a version control or rollback strategy for Docker images Consider adding a version control mechanism or a rollback strategy for Docker images to handle potential issues that might arise from the new image version (enjin/platform:v1.10.0). This could include tagging the previous stable versions or having a quick rollback plan. docker-compose.yml [37] +image: enjin/platform:v1.10.0 - Suggestion importance[1-10]: 6 Why: While this suggestion is useful for maintainability, it is more of a high-level recommendation rather than a specific code improvement. It is correctly derived from the PR code diff.	6