12 breaking releases

0.14.0 Mar 7, 2025
0.12.0 Dec 17, 2024
0.10.0 Oct 29, 2024
0.5.0 Jul 16, 2024

#1441 in WebAssembly

Download history 17204/week @ 2024-12-26 14930/week @ 2025-01-02 31033/week @ 2025-01-09 37777/week @ 2025-01-16 42395/week @ 2025-01-23 28728/week @ 2025-01-30 28722/week @ 2025-02-06 25959/week @ 2025-02-13 47212/week @ 2025-02-20 44399/week @ 2025-02-27 48755/week @ 2025-03-06 69009/week @ 2025-03-13 64288/week @ 2025-03-20 49093/week @ 2025-03-27 40947/week @ 2025-04-03 39010/week @ 2025-04-10

198,323 downloads per month
Used in 38 crates (7 directly)

MIT license

130KB
3K SLoC

wasmer-config

Continuous Integration

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

  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

~9MB
~170K SLoC