5 releases (3 breaking)

0.4.0 Jun 11, 2024
0.3.0 May 23, 2024
0.2.0 May 7, 2024
0.1.1 Apr 25, 2024
0.1.0 Apr 17, 2024

#697 in WebAssembly

Download history 121/week @ 2024-04-15 2199/week @ 2024-04-22 1603/week @ 2024-04-29 4510/week @ 2024-05-06 5057/week @ 2024-05-13 4257/week @ 2024-05-20 4041/week @ 2024-05-27 5025/week @ 2024-06-03 4772/week @ 2024-06-10 4229/week @ 2024-06-17

18,182 downloads per month
Used in 101 crates (5 directly)

MIT license

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

~6MB
~144K SLoC