Skip to content

Releases: gchq/Bailo

v2.2.2

27 Nov 11:16
e2d0623
Compare
Choose a tag to compare

What's Changed

  • Users can now be manually added to models without needing to be selected from the dropdown list.
  • Authorisation checks have been added to all new users on the backend.
  • We have added a migration script that will iterate over every model and run an authorisation check on all existing users, any users that fail this check will be removed from the model. You can find a list of these users in the migrations database by looking at the new metadata property.

Full Changelog: v2.2.1...v2.2.2

v2.2.1

27 Nov 11:11
44e4911
Compare
Choose a tag to compare

What's Changed

  • Implement the create card from template endpoint on the on the python client by @IR96334 in #1471
  • ClamAV Helm config @GB27247 in #1511
  • Improved styling on model export to improve handling of wide content by @ARADDCC002 in #1508
  • Model cards can now be stored in S3 by @JR40159 in #1476
  • Autobuild python docs by @GB27247 in #1477
  • Add additional docker tag and push by @ARADDCC013 in #1515
  • Add ability to hide schemas by @JR40159 in #1516
  • Fix README installation code snippets by @a3957273 in #1524
  • Fixed all pylance warnings in python client by @IR96334 in #1470
  • Added a popover for av results on files by @ARADDCC002 in #1507
  • Prevent access requests and model cards being created using hidden schemas by @JR40159 in #1523
  • Added another authorisation check after updating model to make sure t… by @ARADDCC002 in #1531
  • Added av scanning config to config map by @ARADDCC002 in #1532
  • fix pvc and user by @ARADDCC013 in #1553
  • Added a new endpoint for getting user permissions and added better UI handling of user permissions @ARADDCC012 in #1529
  • Added a check for date widgets to stop it displaying todays date inco… by @ARADDCC002 in #1550
  • Record who exports a model by @JR40159 in #1566
  • Changed clickable area on model overview page ACTIONS button dropdown menu in #1567
  • Added templating and access requests buttons to the new model create screen in #1563
  • Fix python docs building on pages by @GB27247 in #1513
  • Bump tsx from 4.16.5 to 4.19.1 in /backend by @dependabot in #1540
  • Fix landing page by @JR40159 in #1572
  • Fix overflow wrap on model card summary in #1571
  • Python docs by @JR40159 in #1583
  • Remove old information from README by @JR40159 in #1586
  • Fix the AWS packages to a working version by @JR40159 in #1588
    *Removal of legacyBehaviour from next.js links in #1573
  • Fixed an issue where python docs were no longer working locally by @JR40159 in #1585
  • Improve developer logging of requests by @a3957273 in #1394
  • Fixed an issue whereby frontend node server was starting up on the wrong address by @ARADDCC002 in #1587
  • File scanning connector to handle multiple AV tools by @ARADDCC002 in #1514
  • Deleted access request no loger appear on the "your reviews" page by @PE39806 in #1591
  • Implement permissions context by @ARADDCC002 in #1594
  • Update build system to flit_core by @takluyver in #1592
  • Split out the enabling of mirrored models into enabling import and export by @JR40159 in #1614
  • ModelScan REST API by @PE39806 in #1612
  • Replacec GitHub artifact v3 with v4 by @PE39806 in #1615
  • Dockerise our ModelScan application by @PE39806 in #1621
  • Updated backend test config by @ARADDCC012 in #1625
  • Refactor release export to export releases artefacts as separate S3 uploads by @ARADDCC012 in #1617
  • Correct typo in default config by @PE39806 in #1627
  • Allow for auditing of new model cards during import by @ARADDCC012 in #1630
  • Feature/bai 1459 create a new file scan connector for modelscan by @PE39806 in #1628

New Contributors

Full Changelog: v2.2.0...v2.2.1

v2.2.0

03 Sep 15:04
a2be4cd
Compare
Choose a tag to compare

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

v2.1.1

14 Aug 14:54
69b7eb2
Compare
Choose a tag to compare

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

v2.1.0

22 Jul 16:17
d9be9ef
Compare
Choose a tag to compare

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

Bailo v2.0.0

11 Jun 09:25
3af6bd3
Compare
Choose a tag to compare

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

Bailo v0.6.1

09 May 16:37
f64991c
Compare
Choose a tag to compare

Fixes

  • Unit tests were not passing for 'MetadataCard'

Bailo v0.6.0

09 May 15:18
bd1cc0c
Compare
Choose a tag to compare

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.

v0.0.5

08 Mar 16:06
f74f1d9
Compare
Choose a tag to compare

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

v0.0.4

15 Dec 16:51
b7c53df
Compare
Choose a tag to compare

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.