wasmer-toml
| Crates.io | wasmer-toml |
| lib.rs | wasmer-toml |
| version | 0.10.0 |
| source | src |
| created_at | 2022-12-19 15:47:29.565776 |
| updated_at | 2024-04-09 11:59:56.447487 |
| description | A parser for the wasmer.toml format used by Wasmer |
| homepage | https://wasmer.io/ |
| repository | https://github.com/wasmerio/wasmer-toml |
| max_upload_size | |
| id | 741380 |
| size | 62,854 |
Felix Schütt (fschutt)
documentation
README
The wasmer.toml Format
(API Docs)
A parser for the wasmer.toml file used by Wasmer.
For Developers
Releasing
This repository uses Release Please to automate a lot of the work around creating releases.
Every time a commit following the Conventional Commit Style is merged
into main, the release-please.yml
workflow will run and update the "Release PR" to reflect the new changes.
For commits that just fix bugs (i.e. the message starts with "fix: "), the
associated crate will receive a changelog entry and a patch version bump.
Similarly, adding a new feature (i.e. "feat:") does a minor version bump and
adding breaking changes (i.e. "fix!:" or "feat!:") will result in a major
version bump.
When the release PR is merged, the updated changelogs and bumped version numbers
will be merged into the main branch, the release-please.yml workflow will
automatically generate GitHub Releases, and CI will publish the crate if
necessary.
TL;DR:
- Use Conventional Commit Messages whenever you make a noteworthy change
- Merge the release PR when ready to release
- Let the automation do everything else
License
This project is licensed under the MIT license (LICENSE or http://opensource.org/licenses/MIT).
It is recommended to always use cargo crev to verify the
trustworthiness of each of your dependencies, including this one.