wasmer-config
| Crates.io | wasmer-config |
| lib.rs | wasmer-config |
| version | 0.700.0-rc.1 |
| created_at | 2024-04-17 13:59:10.802884+00 |
| updated_at | 2026-01-23 15:48:52.044084+00 |
| description | Configuration types for Wasmer. |
| homepage | https://wasmer.io/ |
| repository | https://github.com/wasmerio/wasmer |
| max_upload_size | |
| id | 1211430 |
| size | 168,637 |
Syrus Akbary (syrusakbary)
documentation
README
wasmer-config
(API Docs)
Provides configuration types for 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.