Skip to content

Add release build for containers #419

Description

@kdvalin

Once we cut a new release, a container with the corresponding tag should be created.

In general the scheme should be the following:
2: Major version 2.x.x, useful to make sure that no breaking changes affects other uses. Will change once a later 2.x.x version is published.
2.0: Pins to 2.0.x, the specific minor release. Will change once a later version in 2.0.x stream is published
2.0.0: Pins to 2.0.0 specifically, will not change once pushed.
latest: Tracks main which is used for new feature development and breaking changes.

Metadata

Metadata

Assignees

Labels

pr_approved[Automatic Label] Issue has an approved PR

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions