Metadata-Version: 2.4
Name: cobotar-protocol
Version: 0.3.3
Summary: Protocol and more for the cobotar project
Project-URL: Homepage, https://cobotar.org
Project-URL: Documentation, https://cobotar.org/protocol
Project-URL: Repository, https://github.com/cobotar/protocol.git
Project-URL: Bug Tracker, https://github.com/cobotar/protocol/issues
Project-URL: Changelog, https://github.com/cobotar/protocol/blob/master/CHANGELOG.md
Author-email: Rasmus Lunding <rsl@cs.au.dk>
Maintainer-email: Rasmus Lunding <rsl@cs.au.dk>
Keywords: ar,cobot,protocol
Classifier: Programming Language :: Python
Requires-Python: >=3.8
Description-Content-Type: text/markdown

# protocol
A collection of protobuf messages

Current version: 0.3.3


## Tagging
In accordance with [get-next-version](https://github.com/marketplace/actions/get-next-version);
you should prefix your commit messages with one of the following keywords:
* `chore` – used for maintenance, does not result in a new version
* `fix` – used for bug fixes, results in a new patch version (e.g. from `1.2.3` to `1.2.4`)
* `feat` – used for introducing new features, results in a new minor version (e.g. from `1.2.3` to `1.3.0`)
* `feat!` – used for breaking changes, results in a new major version (e.g. from `1.2.3` to `2.0.0`)
