Skip to content
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

Notify users of new updates #846

Open
jeffchuber opened this issue Jul 18, 2023 · 3 comments · May be fixed by #1536
Open

Notify users of new updates #846

jeffchuber opened this issue Jul 18, 2023 · 3 comments · May be fixed by #1536
Assignees
@tazarov
Labels
by-chroma taz-sprint-2 to-discuss

Comments

@jeffchuber
Copy link
Contributor

like this

Screenshot 2023-07-18 at 2 46 57 PM
@jeffchuber
Copy link
Contributor Author

I think this could also be used to help developers locate help and our github. One way of doing this is to have a message.json that is checked into the repo.... that makes updating this quite easy. We could take it one step further and have the client callout (if allowed and able) to the version of message.json currently on main or hosted elsewhere....

@jeffchuber
Copy link
Contributor Author

think more about

  • compatibility between releases
  • confidence about non-breaking changes in new releases
  • downgrade support

@jeffchuber jeffchuber self-assigned this Sep 13, 2023
@HammadB HammadB assigned tazarov and unassigned jeffchuber Dec 8, 2023
@tazarov
Copy link
Contributor

tazarov commented Dec 15, 2023 •
edited
Loading

The way that pip does it is by fetching pypi's package info. We can use that to nudge users to upgrade.

Using pypi will not help us with version compatibility - I have a WIP PR for creating a compatibility matrix that can be published and used for version compatibility between local clients (Persistent/Ephemeral) and remote clients (Http and Cloud) - this will knock 1) and 2) from the above list.

@jeffchuber Regarding downgrade support, what is your mental model here? Somehow, advise users how to downgrade versions?

tazarov added a commit to amikos-tech/chroma-core that referenced this issue Dec 15, 2023
@tazarov
feat: Added Chroma client upgrade check
f1f774d 
- __version__ is now exported at chromadb package level
- New check against pypi for latest chroma version (failures are ignored)

Refs: chroma-core#846
@tazarov tazarov linked a pull request Dec 15, 2023 that will close this issue
Open
1 task
tazarov added a commit to amikos-tech/chroma-core that referenced this issue Dec 15, 2023
@tazarov
fix: Adding pytest-httpserver to dev requirements
c56faeb 
Refs: chroma-core#846
tazarov added a commit to amikos-tech/chroma-core that referenced this issue Dec 20, 2023
@tazarov
fix: Adding pytest-httpserver to dev requirements
ca72402 
Refs: chroma-core#846
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tazarov tazarov

Labels
by-chroma taz-sprint-2 to-discuss
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ENH]: Chroma client upgrade check amikos-tech/chroma-core
4 participants
@jeffchuber @tazarov @HammadB @itaismith