chore: update versions and fix license

[jamescalam]

PR Type

Enhancement, Documentation

---

Description

• Updated the __version__ in semantic_router/__init__.py from "0.0.46" to "0.0.50".
• Updated the project version in pyproject.toml from "0.0.49" to "0.0.50".
• Changed the license in pyproject.toml from a file reference to "MIT".

---

Changes walkthrough 📝

	Relevant files
Enhancement	__init__.py Bump version in `__init__.py` to 0.0.50                                    semantic_router/init.py Updated the __version__ from "0.0.46" to "0.0.50". +1/-1
Documentation	pyproject.toml Update version and change license to MIT in `pyproject.toml` pyproject.toml Updated the project version from "0.0.49" to "0.0.50". Changed the license from a file reference to "MIT". +2/-4

---

💡 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: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review None

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Ensure consistent versioning across project files It's recommended to use semantic versioning consistently. Since the version in pyproject.toml was updated from '0.0.49' to '0.0.50', the version in init.py should also be updated from '0.0.46' to '0.0.50' to maintain consistency across the project. semantic_router/init.py [7] +__version__ = "0.0.50" - Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies the need for consistent versioning across project files, which is crucial for maintainability and avoiding confusion.	9
Legal	Verify and correct the license specification to ensure legal coverage The license information in pyproject.toml was changed from a reference to a LICENSE file to a direct "MIT" string. Ensure that this change reflects the project's licensing intentions accurately, as direct string might not provide the same legal coverage or detail as the LICENSE file. pyproject.toml [17] -license = "MIT" +license = {file = "LICENSE"} Suggestion importance[1-10]: 8 Why: The suggestion addresses a potential legal issue by recommending the use of a LICENSE file reference, which typically provides more comprehensive legal coverage than a simple string.	8
Best practice	Implement version control mechanisms to manage version updates Consider adding a version control to ensure that the version number updates are tracked and managed properly. This can be done by adding a script or a CI/CD pipeline step that checks version consistency across different files. pyproject.toml [3] +version = "0.0.50" - Suggestion importance[1-10]: 7 Why: The suggestion is valuable for long-term maintainability and best practices, although it is not immediately critical for the current PR.	7