Skip to content

Plan for versioning the "models" repo and plan for release #167

@puja-trivedi

Description

@puja-trivedi

For models:

  • create a dev_release_* branch that contains all the changes for a future release (so no more separate pushes to main branch)
    • perhaps it could be just dev and this branch name should be added to the GA workflows in places where we have main
  • when a release is created all models irrespective of if changes were made to the model will get upgraded to the newest version
  • adding version value to all the yaml files
  • create GA that updates the version with each release

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions