update the lock file with newer dependency versions

[ckeshava]

High Level Overview of Change

Update the versions of dependencies in the lock file. This is an attempt to resolve the CI errors. Here is an example

I have deleted the existing lock file and re-generated the poetry.lock file in this PR. All the changes have been auto-generated by the poetry install command.

This PR should fix other failing PRs, such as this one.

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

Did you update CHANGELOG.md?

• Yes
• No, this change does not impact library users
  Changes to dependency versions should not affect external APIs.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• poetry.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	sphinx@​7.4.7
	docutils@​0.21.2
	click@​8.1.7 ⏵ 8.1.8	+4
	pyflakes@​3.4.0
	pygments@​2.18.0 ⏵ 2.19.2	+1
	anyio@​4.9.0
	babel@​2.16.0 ⏵ 2.17.0	+1
	urllib3@​2.5.0
	charset-normalizer@​3.4.0 ⏵ 3.4.2
	certifi@​2024.8.30 ⏵ 2025.6.15	+1
	exceptiongroup@​1.2.2 ⏵ 1.3.0
	sphinxcontrib-applehelp@​2.0.0
	pytz@​2024.2 ⏵ 2025.2	+1
	sphinxcontrib-serializinghtml@​2.0.0
	sphinxcontrib-htmlhelp@​2.0.6
	attrs@​24.2.0 ⏵ 25.3.0	+1
	pycodestyle@​2.14.0
	platformdirs@​4.3.8
	wrapt@​1.17.0 ⏵ 1.17.2
	zipp@​3.23.0
	sphinxcontrib-devhelp@​1.0.6
	markupsafe@​3.0.2
	importlib-metadata@​8.7.0
	docstring-parser-fork@​0.0.9 ⏵ 0.0.12
	snowballstemmer@​2.2.0 ⏵ 3.0.1	+1
	alabaster@​0.7.16
	sphinxcontrib-qthelp@​2.0.0
	mypy-extensions@​1.0.0 ⏵ 1.1.0
	pydoclint@​0.5.13 ⏵ 0.5.19	+4

View full report

[Patel-Raj11]

The reason of the failure is still not clear to me. But these dependency updates won't harm if it unblocks other ongoing PR's.

[ckeshava]

The reason of the failure is still not clear to me. But these dependency updates won't harm if it unblocks other ongoing PR's.

I agree, I don't have a good root-cause-analysis. However, the updated poetry.lock appears to be the only difference between the this and the other failing PRs.

If the issue of failing CI still persists (after merging this PR), we can explore other solutions.