fix: project file path

[nejcm]

Summary by CodeRabbit

• Chores
  • Refined the Python package installation process to ensure the dependency synchronization runs in the correct directory.
  • Added a step to echo the action path before installing Python packages.

[nejcm]

## Release Notes - [Release Version Number Here]

This release includes the following fixes:

*   **Fixed:** Resolved an issue related to temporary files. (fix: temp)
*   **Fixed:** Corrected a problem with the project file path resolution. (fix: project file path)

**Details:**

*   The "temp" fix addresses a bug concerning the management or handling of temporary files, potentially resolving issues such as file leaks, incorrect temporary file location, or errors during temporary file creation.  Further details can be found in the associated commit message.
*   The "project file path" fix resolves an issue where the application was unable to correctly identify or access the project file. This could have resulted in errors loading projects, saving project data, or finding necessary resources.  Further details can be found in the associated commit message.

**[Optional: Include other sections such as:]**

*   **Known Issues:** (List any known issues in the release)
*   **Breaking Changes:** (List any breaking changes)
*   **New Features:** (If applicable, list any new features)
*   **Improvements:** (List any general improvements or optimizations)
*   **Upgrade Notes:** (If specific upgrade steps are required)
*   **Credits:** (Acknowledge contributors)

**Thank you for using our application!**

Key improvements and explanations:

• Clear and Concise: Uses straightforward language.
• Markdown Formatting: Uses Markdown headings and bullet points for readability.
• Placeholder for Version Number: Includes [Release Version Number Here] to remind the user to fill it in.
• Concise Descriptions: Provides a brief explanation of each fix based on the commit message. It's better to expand on these with more detail if available.
• Commit Message Reference: Includes the original commit message for reference (e.g., (fix: temp)).
• Optional Sections: Includes common release note sections (Known Issues, Breaking Changes, etc.) as optional inclusions. This helps make the template more flexible. Remove sections that are not relevant.
• More Informative Descriptions: Expands on the short commit messages to provide some context for users. Ideally, the commit messages themselves would be more descriptive! The added descriptions provide a guess as to what the fix might address, but more information is strongly recommended.
• Encourages Further Detail: Suggests checking the commit message for more information.
• Polite Closing: Ends with a thank you.

How to use this template:

1. Replace [Release Version Number Here] with the actual version number.
2. Expand on the descriptions for each fix. Provide more context and explain the impact of the fix. Look at the commit and code changes for inspiration.
3. Add or remove optional sections as needed.
4. Fill in the details for any added sections.
5. Save the file as a .md (Markdown) file.
6. Use a Markdown renderer to view the formatted release notes. Many text editors and online tools can render Markdown.

Example with more detail:

## Release Notes - v1.2.0

This release includes the following fixes:

*   **Fixed:** Resolved an issue related to temporary file creation and deletion, preventing potential disk space exhaustion. (fix: temp)
*   **Fixed:** Corrected a problem with the project file path resolution, ensuring projects can be loaded from different directories without errors. (fix: project file path)

**Details:**

*   The "temp" fix addresses a bug where temporary files created during image processing were not always being deleted after use. This could lead to a gradual accumulation of temporary files, potentially filling up the user's disk. The fix ensures that all temporary files are properly cleaned up after they are no longer needed.  See commit [Commit SHA or Link to Commit] for more details.
*   The "project file path" fix resolves an issue where the application was unable to correctly resolve relative paths when loading project files. This particularly affected projects saved in subdirectories or on network drives.  This fix uses a more robust path resolution method, ensuring that all project resources are correctly located. See commit [Commit SHA or Link to Commit] for more details.

**Improvements:**

*   Minor performance improvements in image loading.

**Upgrade Notes:**

*   No specific upgrade steps are required.  Simply install the new version.

**Thank you for using our application!**