Skip to content

Figure out versioning number handling #1106

@Robin481

Description

@Robin481

We haven't really updated the Skills version in recent history.

We should probably define how we handle the versioning and when we update the number.

It would make sense in my mind to always increment the patch number for each PR.

We could probably just follow semantic versioning https://semver.org/

TODO:

  • Define how we handle versioning and document in the README
  • Make sure current PRs set a relevant number
  • Figure out how we can handle versioning between multiple PRs
  • Maybe we can have some form of bot that automatically sets the version number (create follow up ticket if necessary)

Metadata

Metadata

Assignees

Labels

planneeds to be planned

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions