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.

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

docs: fix minor warning #5089

Merged
merged 2 commits into from
Jun 24, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion argilla/docs/how_to_guides/migrate_from_legacy_datasets.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This guide will help you migrate task specific datasets to Argilla V2. These do
To follow this guide, you will need to have the following prerequisites:

- An argilla 1.* server instance running with legacy datasets.
- An argilla >=1.29 server instance running. If you don't have one, you can create one by following the [Argilla installation guide](../../getting_started/installation.md).
- An argilla >=1.29 server instance running. If you don't have one, you can create one by following the [Argilla installation guide](../getting_started/installation.md).
- The `argilla` sdk package installed in your environment.

If your current legacy datasets are on a server with Argilla release after 1.29, you could chose to recreate your legacy datasets as new datasets on the same server. You could then upgrade the server to Argilla 2.0 and carry on working their. Your legacy datasets will not be visible on the new server, but they will remain in storage layers if you need to access them.
Expand Down
2 changes: 1 addition & 1 deletion argilla/docs/reference/argilla/records/records.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ for record in dataset.records(with_metadata=True):
record.metadata = {"department": "toys"}
```

For changes to take effect, the user must call the `update` method on the `Dataset` object, or pass the updated records to `Dataset.records.log`. All core record atttributes can be updated in this way. Check their respective documentation for more information: [Suggestions](suggestions.md), [Responses](responses.md), [Metadata](metadata.md), [Vectors](vectors/md).
For changes to take effect, the user must call the `update` method on the `Dataset` object, or pass the updated records to `Dataset.records.log`. All core record atttributes can be updated in this way. Check their respective documentation for more information: [Suggestions](suggestions.md), [Responses](responses.md), [Metadata](metadata.md), [Vectors](vectors.md).


---
Expand Down
2 changes: 1 addition & 1 deletion docs/_source/getting_started/argilla.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
```{admonition} Argilla 2.x
:class: danger
We are announcing that Argilla 1.29 is the final minor release for Argilla 1.x. Although we will continue to release bug fixes for this version, we will neither be adding nor removing any functionalities. Instead, we will focus our efforts on Argilla 2.x. Argilla 1.29 will reach its end-of-life on June 20, 2025.
Looking for documentation for Argilla 2.x? Visit the docs [here](https://argilla-io.github.io/argilla/dev/)!
Looking for documentation for Argilla 2.x? Visit the docs [here](https://argilla-io.github.io/argilla/)!
```

<div class="social social--sidebar" style="margin-top: 1em; display: flex; justify-content: right; gap: 8px">
Expand Down
Loading