Release v0.6.4

[marcorosa]

Added

• support for gemini-2.5-flash-lite model

[github-actions]

This update primarily consists of upgrading various dependencies and actions used in the project. These changes improve stability and functionality by leveraging newer versions of GitHub actions, Python dependencies, and frontend packages. The modifications span backend configurations, GitHub workflows, and frontend package upgrades, reflecting an effort to keep the codebase modern and efficient.

Walkthrough

• Chore: Upgraded actions/checkout from version v5 to v6 across multiple GitHub workflows to maintain compatibility and performance.
• Chore: Updated backend dependencies, including sap-ai-sdk-gen, faiss-cpu, and others, reflecting improvements in stability and new features.
• Chore: Updated frontend dependencies and development tools such as @angular packages and typescript, enhancing frontend application stability and performance.
• New Feature: Added new model 'gemini-2.5-flash-lite' in the backend llm.py.
• Versioning: Incremented project version numbers in both the backend (0.6.3 to 0.6.4) and the frontend (0.0.9 to 0.0.10) to align with the updates.

_{Model: gpt-4o-2024-08-06 | Prompt Tokens: 2214 | Completion Tokens: 246}

[github-actions]

Here's a friendly code review enhanced by AI assistance. These suggestions are based on patterns and predictions, so please use your best judgment about what fits your project. You're the expert on your code's goals and context—AI simply offers additional perspective to support your decision-making process.

---

Always critique what AI says. Do not let AI replace YOUR I.
_{Model: claude-sonnet-4-20250514 | Prompt Tokens: 3860 | Completion Tokens: 664}

[github-actions]

Good practice updating to actions/checkout@v6. This ensures you're using the latest version with security improvements and bug fixes. The v6 version provides better performance and enhanced security features compared to v5.

[github-actions]

Adding support for 'gemini-2.5-flash-lite' model is good for providing users with more options. Consider documenting the differences between the lite and full versions in your documentation to help users choose the appropriate model for their use case.

[github-actions]

The dependency updates look good and follow semantic versioning principles. However, consider adding version constraints for better dependency management:

'sap-ai-sdk-gen[all]>=5.9.0,<6.0.0',
'faiss-cpu>=1.13.0,<2.0.0',
'unstructured>=0.18.21,<0.19.0',
'ollama>=0.6.1,<0.7.0',

This prevents automatic updates to major versions that might introduce breaking changes.

[github-actions]

The Angular dependency updates are well-coordinated - all Angular packages are updated to the same version (20.3.15), which is important for compatibility. The caret (^) prefix allows for patch updates while preventing minor/major version conflicts. Consider pinning exact versions for production builds to ensure reproducible deployments:

"@angular/core": "20.3.15",
"@angular/common": "20.3.15"

[github-actions]

The devDependencies updates are consistent and maintain compatibility. The ESLint-related packages are properly updated together, which is crucial for maintaining linting consistency across the project.