Releases: digicatapult/bridgeAI-regression-model-training
Releases · digicatapult/bridgeAI-regression-model-training
Release v0.6.5
add codeowners (#16) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [ ] I have commented my code, particularly in hard-to-understand areas. - [ ] I have 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. - [ ] New and existing unit tests pass locally with my changes. ## PR Type - [x] Chore ## Linked tickets <!-- If this PR is linked to a JIRA ticket or Github Issue, please provide the ticket URL here. --> ## High level description Add codeowners file and update poetry install command in dockerfile. ## Detailed description <!-- A detailed description of the feature and if possible describe how has been implemented. --> ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Latest Release v0.6.5
Release v0.6.4
fix incorrect model uri (#15) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have 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] New and existing unit tests pass locally with my changes. ## PR Type - [x] Bug Fix ## Linked tickets <!-- If this PR is linked to a JIRA ticket or Github Issue, please provide the ticket URL here. --> ## High level description Fix an issue with model uri that was failing to pull the registered model. ## Detailed description <!-- A detailed description of the feature and if possible describe how has been implemented. --> ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Release v0.6.3
fix file move issue (#14) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have 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] New and existing unit tests pass locally with my changes. ## PR Type - [x] Bug Fix ## Linked tickets <!-- If this PR is linked to a JIRA ticket or Github Issue, please provide the ticket URL here. --> ## High level description ensure safe move of file from source to destination. ## Detailed description Deals with `OSError: Invalid cross-device link` when one is on a local disk and the other is on an external disk or a network-mounted volume). Refer - https://stackoverflow.com/questions/42392600/oserror-errno-18-invalid-cross-device-link ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Release v0.6.2
fix dvc pull command (#13) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have 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. - [x] New and existing unit tests pass locally with my changes. ## PR Type - [x] Bug Fix ## Linked tickets <!-- If this PR is linked to a JIRA ticket or Github Issue, please provide the ticket URL here. --> ## High level description dvc pull command requires the name of the remote instead of the dvc s3 url ## Detailed description <!-- A detailed description of the feature and if possible describe how has been implemented. --> ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Release v0.6.1
fix env var read default values from config (#12) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have 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] New and existing unit tests pass locally with my changes. ## PR Type - [x] Bug Fix ## Linked tickets <!-- If this PR is linked to a JIRA ticket or Github Issue, please provide the ticket URL here. --> ## High level description Fix default env var read from config file ## Detailed description <!-- A detailed description of the feature and if possible describe how has been implemented. --> ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Release v0.6.0
modify train script to use right dvc remote (#11) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have 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] New and existing unit tests pass locally with my changes. ## PR Type - [x] Feature - [x] Documentation Update ## Linked tickets <!-- If this PR is linked to a JIRA ticket or Github Issue, please provide the ticket URL here. --> ## High level description Configure the training script to use the right dvc remote. ## Detailed description <!-- A detailed description of the feature and if possible describe how has been implemented. --> ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Release v0.5.0
Feature/automate model promotion (#10) # Pull Request ## Checklist - [x] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have 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. - [x] New and existing unit tests pass locally with my changes. ## PR Type Please delete options that are irrelevant. - [x] Feature - [x] Documentation Update ## Linked tickets https://digicatapult.atlassian.net/browse/BRID-124 ## High level description <!-- One paragraph explanation of the feature. --> ## Detailed description Use mlflow apis to automate the model registration with a specified name and for adding an alias. Add integration tests: For the model registration to work, it was required to bring the mlflow up with a backend store (sqlite in this case). Hence we updated the docker compose yaml file. ## Describe alternatives you've considered <!-- A clear and concise description of the alternative solutions you've considered. Be sure to explain why the existing customisability isn't suitable for this feature. --> ## Operational impact <!--- A description of any operational considerations associated with the change. Is there anything in particular we should be looking at when deploying the change to make sure it is working as intended. If something goes wrong will any special actions be needed to revert the change. --> ## Additional context <!-- Add any other context or screenshots about the feature request here. -->
Release v0.4.0
Adding dockerhub release method (#9) # Pull Request ## Checklist - [X] Have you read Digital Catapult's [Code of Conduct](https://github.com/digicatapult/.github/blob/main/CODE_OF_CONDUCT.md)? - [X] I have performed a self-review of my own code. - [X] I have commented my code, particularly in hard-to-understand areas. - [X] I have 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. - [ ] New and existing unit tests pass locally with my changes. ## PR Type Please delete options that are irrelevant. - [X] Chore ## Linked tickets N/A ## High level description Adds dockerhub release mechanism ## Detailed description Adding dockerhub release method so we can push containers to both GHCR and dockerhub so people can use containers without requiring authentication to GHCR. ## Describe alternatives you've considered N/A ## Operational impact N/A ## Additional context N/A
Release v0.3.0
bundle preprocessing and dependencies to the mlflow logged model (#7) * bundle preprocessing and dependancies to the mlflow logged model 1. Create custom MLFlow model to include preprocessing 2. Capture dependancies from the pyproject file and bind it to the logged model 3. Add data schema validation for the data using pandera 4. Update tests * increment version * update readme