10 breaking releases

0.12.0 Dec 17, 2024
0.10.0 Oct 29, 2024
0.5.0 Jul 16, 2024

#988 in WebAssembly

Download history 16448/week @ 2024-10-02 14879/week @ 2024-10-09 12954/week @ 2024-10-16 13110/week @ 2024-10-23 13384/week @ 2024-10-30 12217/week @ 2024-11-06 7891/week @ 2024-11-13 9331/week @ 2024-11-20 10170/week @ 2024-11-27 9931/week @ 2024-12-04 9707/week @ 2024-12-11 6862/week @ 2024-12-18 14385/week @ 2024-12-25 16222/week @ 2025-01-01 26807/week @ 2025-01-08 39544/week @ 2025-01-15

97,430 downloads per month
Used in 41 crates (7 directly)

MIT license

110KB
2.5K 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

~7MB
~137K SLoC