Skip to content

Releases: gchq/Bailo

v2.2.0

03 Sep 15:04
@GB27247 GB27247
v2.2.0
a2be4cd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.2.0 Latest
Latest

Features

  • When deleting a schema resources that are effected will be listed
  • Node versions have been bumped up to 22.6.0

What's Changed

Full Changelog: v2.1.1...v2.2.0

Contributors

dependabot, ARADDCC002, and 4 other contributors
Assets 2
Loading

v2.1.1

14 Aug 14:54
@ARADDCC002 ARADDCC002
v2.1.1
69b7eb2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.1.1

Features

  • Added a getAdminToken script to get an admin token to the registry
  • Tokens are now sourced through an endpoint

What's Changed

Full Changelog: v2.1.0...v2.1.1

Contributors

a3957273, ARADDCC002, and 2 other contributors
Assets 2
Loading

v2.1.0

22 Jul 16:17
@JR40159 JR40159
v2.1.0
d9be9ef
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.1.0

Features

  • Upgraded from Node 18 to Node 22.
  • Added a standalone version of Bailo that runs all of Bailo in a single Docker container.
  • Added utility to import Models from MLFlow via the Python Client.
  • Added the ability to use attach IAM roles to containers when deploying to AWS.
  • Update OpenTelemetry integration to include CPU and memory usage.
  • Ensure that Bailo is compatible with registry version 3.0.0-alpha.1, enabling the use of IAM roles when deploying the registry on AWS.
  • Comment and review responses have been restructured in the backend so that they can be more easily interacted with via the API; this has allowed for a much smoother integration with features such as reactions and editing responses.
  • Added support for data cards.
  • Added Advanced options during data card/model creation, allowing user roles to be assigned immediately.
  • Fixed large file uploads failing to complete.
  • Added ability to create and view data card schemas via the UI.
  • Fixed Cypress tests intermittently failing due to backend not being ready.
  • Fixed a bug where opening a review from the reviews page would incorrectly set the user's role.
  • Conditionally disabled functionality in places to restrict users from performing actions they are not authorised to do. Tooltips have been used to provide guidance to users in these cases.
  • Improved schema selection UI, allowing active/inactive schemas to be shown/hidden in bulk.
  • Added ability to edit comments.

What's Changed

New Contributors

Full Changelog: v2.0.0...v2.1.0

Contributors

dependabot, GCHQDeveloper36, and 10 other contributors
Assets 2
Loading

Bailo v2.0.0

11 Jun 09:25
@a3957273 a3957273
v2.0.0
3af6bd3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Bailo v2.0.0

We're restarting releases, which will occur on a three-weekly basis. This is a catch-all release for the work that has been done over the past year.

What's Changed

Read more

Contributors

dependabot, GCHQDeveloper36, and 12 other contributors
Assets 2
Loading

Bailo v0.6.1

09 May 16:37
@a3957273 a3957273
v0.6.1
f64991c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Bailo v0.6.1

Fixes

  • Unit tests were not passing for 'MetadataCard'
Assets 2
Loading

Bailo v0.6.0

09 May 15:18
@a3957273 a3957273
v0.6.0
bd1cc0c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Bailo v0.6.0

NOTE: This is a significant change to the Bailo repository. Specifically guidelines have been written for upgrading here:
https://gchq.github.io/Bailo/docs/administration/migrations/bailo-0.4

Breaking Changes

  • Changed how schemas are initially added to Bailo. Now set in config.defaultSchemas instead of schema.script. Now is a list of schema objects, instead of a bash script.
  • Model card sidebar now uses role names from schema, instead of hard coded.
  • Removes usage of 'turbopack' to build dependencies, speeding up builds by 7x.
  • Python library client instantiation has been simplified, with less facades in place. See library README for more details.
  • The application now produces two Docker images, a 'frontend' and 'backend' image. See v0.4 migration for more details.
  • Migrated from CJS to ESM for NodeJS dependency management.

Features

  • Python documentation can now be built into a webpage using cd docs && make html
  • Python client can now bundle a variety of frameworks automatically, with no code required.
  • Python tests are not automatically run on GitHub Actions.
  • The latest version of a model is now tagged on the version selector dropdown for easier viewing.
  • Entities (groups, users, etc) can now be relabelled using the generic 'EntityDisplay' component.
  • Editing a model now automatically requests re-approval.
  • We now support all JSON Schema Beta 7 proposals in model card schemas.
  • Helm charts natively support AWS.
  • Added sharp to optimise images prior to display to users.
  • Tests are now run using 'vitest' instead of 'jest'.
  • The compliance graph now has a key.

Fixes

  • Banner could never be displayed due to 'enable' vs 'enabled' differences.
  • Logging had to be disabled on OpenShift clusters due to '$' in key, now filtered out.
  • Local configuration can no longer be committed to GitHub.
  • Authorisation unit tests now pass regardless of 'AuthorisationBase' configuration.
  • Python library now supports PKI.
  • Fix UI not able to serve images.
  • The wrong person was responsible for approving models, changed it from the deployment owner to the model manager.
  • Added a useful error message for when a new version is uploaded to a non-existent model.
  • The deployment name is now displayed on the model review page when approving a deployment.
  • Application now successfully responds to 'SIGINT' and 'SIGTERM' signals.
  • Swagger can now upload docker images to the upload endpoint.
  • The deployment and upload form can now be submitted multiple times, and does not break on the first error.
  • The documentation now uses a static file directory listing. The page no longer requires any external network requests.
  • The base path was incorrectly set for the Bailo landing page.
  • Increase maximum file size Bailo can cope with, by streaming data instead of keeping it in memory.
Assets 2
Loading

v0.0.5

08 Mar 16:06
@ARADDCC002 ARADDCC002
v0.0.5
f74f1d9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.5

Features

  • Deployments are no longer coupled to versions. Whenever a deployment is requested, it will be made available for all current approved versions, and whenever a new version of a model is requested, all existing deployments will be updated to be available for the new version.
  • Ungoverned deployments are now available. This is where you can request a deployment of a model without needing to go through the request form and approval process. Ungoverned deployments are appropriately labelled as such
  • Failed builds can now be retried
  • Model files can now be viewed in the UI
  • Admins can now upload new schemas via the UI using the new "schemas" page. Please note: the "designer" table is currently under development and is not supported.
  • When selecting a deployment's download commands window, it will now default to the latest version, and also add a tag to it stating that it's the latest

Fixes

  • Fixed an issue where the model's latest version data wasn't been updated
  • Notifications are now sent to model owner, not the person approving the request. Also fixed an issue where email reports were not displaying the username correctly
  • Previously approved deployments than are subsequently declined will now be unavailable from the registry
  • Admin logs should now appear correctly
  • General improvement to logging
  • Upped various dependency versions
  • Deployment page updates correctly when resetting approvals
  • Removed some out of date configuration values
  • Deployments can now only be requested for approved versions
  • Various fixes to the Python client
Assets 2
Loading

v0.0.4

15 Dec 16:51
@ARADDCC002 ARADDCC002
v0.0.4
b7c53df
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.4

Features

  • Versions can now be deleted. Deployments and models will also be deleted if they are only associated with the version that was deleted.
  • Requests on the review page now display the model version so that it is clearer when reviewing multiple versions of the same model.
  • Selenium has been replaced with Cypress for end-to-end tests.
Assets 2
Loading

v0.0.3

16 Nov 19:15
@ARADDCC002 ARADDCC002
v0.0.3
719d402
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.3

Features

  • Improved multi-line support for schemas
  • Documentation improvements
  • Formatting for tables for in-app documentation pages (.mdx files) has been improved
  • Next and previous navigation buttons have been added to the in-app documentation pages
  • You can now navigate to the main page by clicking the "Bailo" text in the toolbar
  • When uploading models you can now use Docker images
  • Model files are now exportable by default
  • Support for Cypress tests has been added
  • By default, version and deployment logs are not returned via the API unless specifically requested
  • Various Helm improvements
  • Previously reviewed versions/deployments can now be viewed in an archived tab, and can also be amended
  • Added an alert to the version page if you're a reviewer and you're viewing since it has been edited
  • Deployment metadata can now be copied to the clipboard under the "settings" tab
  • There is now a "Back to model" button on the deployments page.

Fixes

  • Various parts of the UI has been altered so it displays correctly in dark mode
  • The metadata display for models and deployments now correctly displays any multi-line content
  • Help & support page is now more visually responsive
  • Fixed an issue where the version page was not updating after being edited
  • Removed unnecessary white-space in upload form
Assets 2
Loading

v0.0.2

05 Oct 09:31
@ARADDCC002 ARADDCC002
v0.0.2
726aeda
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.2

Features

  • When uploading a new version, you can now select whether or not you want the raw code/binary files to be able to downloaded by other users.
  • You can now upload a new version as just a model card.
  • Under the help & support section there is now a link to in-app documentation. More pages can easily be added in the future.
  • When viewing a model you can select the approvals chip to see which users are assigned to that version and the status of their review.
  • Various text fields in the form page have been changed so that they increase in size when lots of content is added.

Fixes

  • When uploading a new version with an invalid "mode" property, it will now gracefully send an error to the uploader.
  • Added more information to some of our logs.
  • Reviewers who have been removed from a model will no longer still be able to review that model.
  • When changing section in the upload form, the view will be scrolled to the top of the next section.
Assets 2
Loading