chore: release v0.0.46

[jamescalam]

PR Type

other

---

Description

• Bumped the version number from "0.0.45" to "0.0.46" in semantic_router/__init__.py.
• Updated the version field in pyproject.toml to "0.0.46".

---

Changes walkthrough 📝

	Relevant files
Miscellaneous	__init__.py Bump version number in `__init__.py`                                          semantic_router/init.py Updated the __version__ attribute from "0.0.45" to "0.0.46". +1/-1      pyproject.toml Update version in `pyproject.toml`                                              pyproject.toml Updated the version field from "0.0.45" to "0.0.46". +1/-1

---

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

[github-actions]

PR Description updated to latest commit (2556cb0)

[github-actions]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the PR involves simple version number updates in two files, which is straightforward and requires minimal review effort.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

Code feedback:

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Use a single source for version number to maintain consistency Consider using a more robust method for managing version numbers, such as reading from a single source like 'pyproject.toml'. This will help avoid inconsistencies and manual errors in version updates across multiple files. semantic_router/init.py [7] -__version__ = "0.0.46" +from importlib.metadata import version +__version__ = version('semantic-router') Suggestion importance[1-10]: 9 Why: This suggestion addresses a significant maintainability issue by proposing a method to avoid inconsistencies and manual errors in version updates across multiple files. It is highly relevant and improves the robustness of the code.	9
Best practice	Automate the version update process to reduce manual errors Ensure that the version number is updated in a consistent and error-free manner by potentially automating this process through CI/CD pipelines, using scripts that update all necessary files simultaneously. pyproject.toml [3] -version = "0.0.46" +version = "0.0.46" # Consider automating this update Suggestion importance[1-10]: 8 Why: Automating the version update process is a best practice that can significantly reduce the risk of manual errors. This suggestion is practical and enhances the reliability of the versioning process.	8