Bailo v0.6.1

Fixes

• Unit tests were not passing for 'MetadataCard'

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.

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

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.

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

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.

v0.0.1

Our first versioned release.

Features

• Improved upload processing, now we use the BuildHandler to reliably run model builds. This process takes care of rollbacks, cleanups and more.
• Dark mode is now supported, enable it in the top-right corner.
• The Python client is now updated to Bailo v2.
• Reviewer names are now added to emails sent on review success / failure.
• The Python client now has unit tests.
• The Bailo application now has over 70% of code paths tested.

Fixes

• Linting was disabled on src, server and other misc folders. This release enables linting on all folders except server, which is being linted in the next release.
• Remove incorrect index preventing multiple different models from having the same version.