Skip to content

[RELEASE] 1.0.13 #4878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 18, 2025
Merged

[RELEASE] 1.0.13 #4878

merged 1 commit into from
Jun 18, 2025

Conversation

jairad26
Copy link
Contributor

@jairad26 jairad26 commented Jun 18, 2025 •
edited
Loading

Description of changes

Release new python client 1.0.13

Test plan

How are these changes tested?

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

@github-actions GitHub Actions
Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@jairad26 Graphite App
Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@jairad26 jairad26 marked this pull request as ready for review June 18, 2025 17:56
@HammadB
Copy link
Collaborator

HammadB commented Jun 18, 2025

https://github.com/chroma-core/chroma/blob/main/RELEASE_PROCESS.md

I suggest we update this with the fact that all the deployments need updating

@jairad26
Copy link
Contributor Author

https://github.com/chroma-core/chroma/blob/main/RELEASE_PROCESS.md

I suggest we update this with the fact that all the deployments need updating

makes sense, Itai made this PR here
#4879

@jairad26 jairad26 merged commit 4ef35d7 into main Jun 18, 2025
114 of 116 checks passed
Inventrohyder pushed a commit to Inventrohyder/chroma that referenced this pull request Aug 5, 2025
@jairad26 @Inventrohyder
[RELEASE] 1.0.13 (chroma-core#4878)
4fddc29 
## Description of changes

Release new python client 1.0.13

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@itaismith itaismith itaismith approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@jairad26 @HammadB @itaismith