-
Notifications
You must be signed in to change notification settings - Fork 377
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
Releases/1.6.0 #2644
Releases/1.6.0 #2644
Conversation
# Description The docker image description is updated on every docker image publication. This PR changes this behavior to update it only when a release event is triggered. **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [x] Bug fix (non-breaking change which fixes an issue) **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) Launching the ci pipeline. **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: Tom Aarsen <[email protected]>
# Description This PR adds a minimal setup for argilla deployment in a Kubernetes cluster. Closes #2144 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [x] Improvement (change adding some improvement to an existing functionality) - [x] Documentation update --------- Co-authored-by: david <[email protected]>
# Description This is the feature branch including all the changes related with new database support. --------- Co-authored-by: Francisco Aranda <[email protected]> Co-authored-by: frascuchon <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: keithCuniah <[email protected]> Co-authored-by: Natalia Elvira <[email protected]> Co-authored-by: Daniel Vila Suero <[email protected]> Co-authored-by: David Berenstein <[email protected]>
# Description This PR changes how `copyright` docs attribute is set. Now instead of a fix string we are getting dynamically the current year. See #2569 (comment) **Type of change** - [x] Improvement (change adding some improvement to an existing functionality) **How Has This Been Tested** - [x] I have locally generated the documentation and I can see that the copyright footer on the generated documentation is showing the current year. **Checklist** - [x] I have merged the original branch into my forked branch. - [x] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [x] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] <del>I have added tests that prove my fix is effective or that my feature works</del> Not necessary. - [ ] <del>I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)</del> Not necessary.
# Description This pull request aligns the image classification tutorial with the correct implementation by displaying images from a URL on the front end. - i.e. `_image_url` in metadata. - install instructions are returned to standard. Closes #2592 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [x] Bug fix (non-breaking change which fixes an issue) **How Has This Been Tested** The notebook has been run with a release v1.5.0 instance of Argilla. **Checklist**
<!--pre-commit.ci start--> updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.254 → v0.0.255](astral-sh/ruff-pre-commit@v0.0.254...v0.0.255) <!--pre-commit.ci end--> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
# Description Main branch for front part of user settings Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. Closes #2496 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [ ] Test A - [ ] Test B **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: keithCuniah <[email protected]> Co-authored-by: José Francisco Calvo <[email protected]> Co-authored-by: Francisco Aranda <[email protected]> Co-authored-by: José Francisco Calvo <[email protected]> Co-authored-by: frascuchon <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: leire <[email protected]> Co-authored-by: Natalia Elvira <[email protected]> Co-authored-by: Daniel Vila Suero <[email protected]> Co-authored-by: David Berenstein <[email protected]> Co-authored-by: leiyre <[email protected]>
#2613) # Description This PR adds a missing step describing the execution of database migrations for developer documentation. Closes #2612 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [x] Documentation update **Checklist** - [x] I have merged the original branch into my forked branch - [x] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [x] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] <del>I have added tests that prove my fix is effective or that my feature works</del> (Not necessary) - [ ] <del>I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)</del> (Not necessary)
# Description Allow to access rule management while rule metrics are pending Note: - this is not the most performant solution since the base-table component is rerendered each time the input change - there is a dirty fix (see RuleDefinition.vue) to ensure the reactivity when the query search change. This correction close this issue #2561 Closes #2117 Close #2561 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [x] Textclassification **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: keithCuniah <[email protected]> Co-authored-by: José Francisco Calvo <[email protected]> Co-authored-by: Francisco Aranda <[email protected]> Co-authored-by: José Francisco Calvo <[email protected]> Co-authored-by: frascuchon <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: leire <[email protected]> Co-authored-by: Natalia Elvira <[email protected]> Co-authored-by: Daniel Vila Suero <[email protected]> Co-authored-by: David Berenstein <[email protected]> Co-authored-by: leiyre <[email protected]>
Co-authored-by: Tom Aarsen <[email protected]>
# Description With this change, the new client is still compatible with an old server version. Ref [#2480](#2480) **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [x] Bug fix (non-breaking change which fixes an issue) **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) N/A **Checklist** - [x] I have merged the original branch into my forked branch - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works
Small spelling fix in the doc
# Description Fixed link to Pages inside of Reference > Argilla UI. **Type of change** - [x] Documentation update **Checklist** - [ ] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [ ] follows the style guidelines of this project - [ ] I did a self-review of my code - [x] I made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #2644 +/- ##
==========================================
+ Coverage 93.63% 94.11% +0.47%
==========================================
Files 158 170 +12
Lines 7853 8727 +874
==========================================
+ Hits 7353 8213 +860
- Misses 500 514 +14
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 3 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
# Description - Remove old default apikey value - Remove old API Key header - Remove old workspace header Closes [#2251](#2251) **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [x] Refactor (change restructuring the codebase without changing functionality) **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
…2626) # Description Updates : - weak labelling styles - messages (weak labelling and dataset settings) - add toast on success/error saving rule Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update - [x] [x] styles **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [ ] Text classification - [ ] dataset settings **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: keithCuniah <[email protected]>
… database (#2650) # Description Adds a new small section for development docs about how to recreate the database from scratch. **Type of change** - [x] Documentation update **How Has This Been Tested** - [x] I have generated the documentation in my development environment and the generated document looks as expected. **Checklist** - [x] I have merged the original branch into my forked branch - [x] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [x] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] <del>I have added tests that prove my fix is effective or that my feature works</del> (Not necessary) - [ ] <del>I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)</del> (Not necessary)
# Description Update messages Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. See #2626 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update - [x] Style **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [ ] Test A **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [ ] I did a self-review of my code - [x] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: keithCuniah <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Tom Aarsen <[email protected]>
# Description Hide the user settings token with a static variable '**** **** **** ****' Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [x] user settings **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
# Description This PR includes an access in the UI, from the header of the dataset, to view the training snippets in a modal window, and to allow copying them. Closes #2475 Closes #2391 **Type of change** - [x] New feature (non-breaking change which adds functionality) **How Has This Been Tested** - [x] new Base Tabs component test - [x] update help Info component test **Checklist** - [x] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [x] follows the style guidelines of this project - [x] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: david <[email protected]> Co-authored-by: Tom Aarsen <[email protected]>
# Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. Closes #<issue_number> **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [ ] Test A - [ ] Test B **Checklist** - [ ] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [ ] follows the style guidelines of this project - [ ] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: leire <[email protected]> Co-authored-by: Tom Aarsen <[email protected]>
…ning workflows (#2574) # Description Hi, this PR contains some preliminary work on the creating of an `Argilla.training` module, which should simplify training workflows for training using Argilla datasets for several common tasks using several common libraries. Initially, it only contains a `ArgillaSetFitTrainer` and an `ArgillaBaseTrainer`. Closes #2504 **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [X] New feature (non-breaking change which adds functionality) **How Has This Been Tested** Not yet implemented tests **Checklist** - [ ] I have merged the original branch into my forked branch - [ ] I added relevant documentation - [ ] follows the style guidelines of this project - [ ] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/) --------- Co-authored-by: Tom Aarsen <[email protected]> Co-authored-by: Alvaro Bartolome <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Tom Aarsen <[email protected]> Co-authored-by: Daniel Vila Suero <[email protected]> Co-authored-by: frascuchon <[email protected]>
# Description Resolves small QA issues w.r.t. text and CSS for code block formatting.
1cc51dc
to
295c98f
Compare
1.6.0
Added
ARGILLA_HOME_PATH
new environment variable (#2564).ARGILLA_DATABASE_URL
new environment variable (#2564).admin
andannotator
(#2564).id
,first_name
,last_name
,role
,inserted_at
andupdated_at
new user fields (#2564)./api/users
new endpoint to list and create users (#2564)./api/users/{user_id}
new endpoint to delete users (#2564)./api/workspaces
new endpoint to list and create workspaces (#2564)./api/workspaces/{workspace_id}/users
new endpoint to list workspace users (#2564)./api/workspaces/{workspace_id}/users/{user_id}
new endpoint to create and delete workspace users (#2564).argilla.tasks.users.migrate
new task to migrate users from old YAML file to database (#2564).argilla.tasks.users.create
new task to create a user (#2564).argilla.tasks.users.create_default
new task to create a user with default credentials (#2564).argilla.tasks.database.migrate
new task to execute database migrations (#2564).release.Dockerfile
andquickstart.Dockerfile
now creates a defaultargilladata
volume to persist data (#2564).Changed
ARGILLA_USERS_DB_FILE
environment variable now it's only used to migrate users from YAML file to database (#2564).full_name
user field is now deprecated andfirst_name
andlast_name
should be used instead (#2564).password
user field now requires a minimum of8
and a maximum of100
characters in size (#2564).quickstart.Dockerfile
image default users fromteam
andargilla
toadmin
andannotator
including new passwords and API keys (#2564).admin
role (#2564).Removed
email
user field (#2564).disabled
user field (#2564).ARGILLA_LOCAL_AUTH_DEFAULT_APIKEY
andARGILLA_LOCAL_AUTH_DEFAULT_PASSWORD
environment variables. Usepython -m argilla.tasks.users.create_default
instead (#2564).