Uses a fixed dart version

[leonardocustodio]

PR Type

enhancement, configuration changes

---

Description

• Updated the Dart version in the Dockerfile from stable to 3.4 to ensure consistency and predictability in builds.
• Added a newline at the end of the Dockerfile to maintain consistent file formatting.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	Dockerfile Pin Dart version and format Dockerfile                                      Dockerfile Changed Dart version from stable to 3.4. Ensured consistent formatting by adding a newline at the end of the file. +2/-2

---

💡 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
Security	Set a non-root user for running the application to enhance security Ensure that the Dockerfile explicitly sets a non-root user for running the application. This is a security best practice to limit the privileges of the application, reducing the risks if the container is compromised. Dockerfile [19] +USER nonroot CMD ["/app/bin/server"] Suggestion importance[1-10]: 9 Why: Setting a non-root user is a crucial security measure that limits the privileges of the application, reducing potential risks if the container is compromised. This suggestion addresses a significant security concern.	9
Best practice	Use a specific version tag for the Dart image to ensure consistent builds Consider using a more specific version tag instead of '3.4' for the Dart image to ensure consistent, reproducible builds. Using a specific version helps avoid potential incompatibilities or unexpected changes when newer versions are released. Dockerfile [1] -FROM dart:3.4 as build +FROM dart:3.4.0 as build Suggestion importance[1-10]: 8 Why: Using a specific version tag for the Dart image is a good practice for ensuring consistent and reproducible builds, as it prevents unexpected changes from newer versions affecting the build process.	8