Skip to content

Conversation

stellasia
Copy link
Contributor

Description

Related to #300

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Documentation update
  • Project configuration change

Complexity

Note

Please provide an estimated complexity of this PR of either Low, Medium or High

Complexity:

How Has This Been Tested?

  • Unit tests
  • E2E tests
  • Manual tests

Checklist

The following requirements should have been met (depending on the changes in the branch):

  • Documentation has been updated
  • Unit tests have been updated
  • E2E tests have been updated
  • Examples have been updated
  • New files have copyright header
  • CLA (https://neo4j.com/developer/cla/) has been signed
  • CHANGELOG.md updated if appropriate

@stellasia stellasia requested a review from a team as a code owner March 11, 2025 15:57
Copy link
Member

@oskarhane oskarhane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did our tests catch the issue? If not, can we add test to make sure something goes red if something similar happens in the future?
other than that, LGTM 🍡

@stellasia stellasia force-pushed the fix/update-anthropic branch from e06cf40 to 325c3dd Compare March 12, 2025 12:28
@stellasia stellasia changed the title Upgrade Anthropic Upgrade Anthropic & clean ruff/mypy stuffs Mar 12, 2025
@stellasia stellasia merged commit 60d8f97 into neo4j:main Mar 12, 2025
7 checks passed
@stellasia stellasia deleted the fix/update-anthropic branch April 15, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants