The cloud is the hosted service. Chrome is the extension you install. The plugin connects LangSave to ChatGPT. Their version numbers do not need to match.
BEFORE YOU UPDATE
Will my versions work together?
Chrome extension 0.1.2 + Cloud 0.2.0✓ Compatible
Keep your current extension and browser token. No reinstall is needed.
ChatGPT plugin 0.1.2 + Cloud 0.2.0✓ Compatible
Keep your current ChatGPT connection. No reconnect is needed.
Both clients connect to the cloud independently. Chrome is optional for ChatGPT practice. A compatible historical cloud release is a record, not a server you can switch to here.
THE COMPLETE RECORDED TREE
Every cloud release, every client.
Compatible means this pairing has been checked. Breaking change means it cannot work as-is. Not verified means we do not yet know.
Follow LangSave’s development and check which versions work together before you update.
+Added A public changelog with a separate release history for cloud, Chrome and the ChatGPT plugin.
+Added A compatibility checker and complete recorded compatibility tree, including guidance for any breaking changes.
+Added Component filters and direct links to individual releases.
~Changed Independent 0.x.y versions: x introduces features; y contains bug fixes only. The leading 0 stays until we explicitly decide to become a standalone app.
The first recorded ChatGPT integration. Add it using the instructions on your account page.
+Added Bring your profile and relevant learning evidence into ChatGPT practice.
+Added Save authorized learning observations, profile preferences and exact conversation excerpts.
+Added Inspect the source history behind a word or phrase, including corrections and retractions.
+Added Sign in to your own LangSave account using OAuth; conversations receive an Early alpha tester notice.
OUR VERSIONING PROMISE
0.x.y, one update at a time.
0
We stay at zero until we explicitly decide to become a standalone app, independent of a GPT subscription. It does not change automatically.
x
Feature updates. New capabilities, removals and other behaviour changes increment this number and reset y to zero. Breaking changes must be called out in the compatibility tree.
y
Bug fixes only. No features, no feature removals, and no breaking compatibility changes hidden in a patch.
For example: a fix to 0.1.2 becomes 0.1.3. A new feature becomes 0.2.0. A cloud update does not automatically bump Chrome or the plugin.
0.1.2 is the first recorded baseline for all three components. These rules apply to releases after that baseline. We have not reconstructed unrecorded earlier versions.