9 releases (5 breaking)

0.10.0 Apr 9, 2024
0.9.3 Apr 9, 2024
0.9.2 Oct 10, 2023
0.9.0 Sep 29, 2023
0.5.0 Dec 19, 2022

#1822 in Parser implementations

Download history 526/week @ 2024-10-17 562/week @ 2024-10-24 586/week @ 2024-10-31 425/week @ 2024-11-07 1137/week @ 2024-11-14 405/week @ 2024-11-21 365/week @ 2024-11-28 436/week @ 2024-12-05 542/week @ 2024-12-12 369/week @ 2024-12-19 338/week @ 2024-12-26 365/week @ 2025-01-02 425/week @ 2025-01-09 341/week @ 2025-01-16 222/week @ 2025-01-23 137/week @ 2025-01-30

1,211 downloads per month
Used in 4 crates (2 directly)

MIT license

54KB
1K SLoC

The wasmer.toml Format

Continuous Integration

(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:

  1. Use Conventional Commit Messages whenever you make a noteworthy change
  2. Merge the release PR when ready to release
  3. 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.

Dependencies

~5MB
~103K SLoC