8 releases (4 breaking)

0.9.2 Oct 10, 2023
0.9.1 Oct 9, 2023
0.9.0 Sep 29, 2023
0.8.1 Sep 29, 2023
0.5.0 Dec 19, 2022

#331 in Parser implementations

Download history 4097/week @ 2023-11-23 3356/week @ 2023-11-30 1695/week @ 2023-12-07 1580/week @ 2023-12-14 2613/week @ 2023-12-21 1655/week @ 2023-12-28 3585/week @ 2024-01-04 2789/week @ 2024-01-11 15397/week @ 2024-01-18 7594/week @ 2024-01-25 14047/week @ 2024-02-01 8823/week @ 2024-02-08 6435/week @ 2024-02-15 7779/week @ 2024-02-22 8400/week @ 2024-02-29 7033/week @ 2024-03-07

31,044 downloads per month
Used in 21 crates (8 directly)

MIT license

53KB
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

~4.5MB
~92K SLoC