Releases: wasmCloud/wadm
v0.12.1
What's Changed
- feat(reuseProviders): Allow capability providers to be reused across components by @ritesh089 in #297
- fix(client): app list topic by @brooksmtownsend in #300
- chore: bump to v0.12.1 for release by @brooksmtownsend in #299
- fix(client): correct delete topic by @brooksmtownsend in #302
- fix(wadm): support empty delete payload by @brooksmtownsend in #305
New Contributors
- @ritesh089 made their first contribution in #297
Full Changelog: v0.12.0...v0.12.1
v0.12.0
What's Changed
- Add support for mounting Kubernetes Secret for nats.creds file by @joonas in #272
- Fix rendering WADM_NATS_CREDS_FILE when creds secret is provided by @joonas in #273
- chore: fix clippy lints by @vados-cosmonic in #275
- feat(*)!: Makes version optional by @thomastaylor312 in #281
- ci(release): use native macos arm64 runner by @brooksmtownsend in #283
- chore: bump to v0.11.2 by @brooksmtownsend in #286
- docs(readme): Update manifest example and language for 1.0 by @ericgregory in #284
- feat(validation): add manifest validation by @vados-cosmonic in #274
- feat(*)!: Breaks wadm into separate crates and creates a new wadm-client by @thomastaylor312 in #287
- chore(wadm): bump to v0.12.0 for release by @brooksmtownsend in #289
- fix(*): Removed unneeded readme keys and update paths by @thomastaylor312 in #290
- fix(*): Bumps wadm crate version by @thomastaylor312 in #291
- fix(wadm): Adds oam schema to wadm crate by @thomastaylor312 in #292
Breaking changes
This version contains a breaking change to the wadm API as well as one big, but backwards compatible change. We inverted the behavior of the delete model API to always delete all versions by default. In practice, it turned out that few users wanted to only delete a specific version. Now the API takes a body that looks like:
{
"version": "1.0"
}
The version field is optional. If it is not set, all versions of a model will be deleted, but if it is set, it will only delete the specific model version given
Additionally, we have now made the version
field in a manifest entirely optional. Versioning sounded like a good idea, but caused more headache than it was worth, especially for local development. You can still specify a version and it still must be unique, but by default, wadm will generate a ULID for the version of the model. This means you can get the original insertion order of models by sorting on the version. Old manifests will still continue to function properly if they have the version
field set.
New crates
This release also marks the launch of a few new crates for wadm. Before, everything was part of the wadm
crate and there was no specific client library. Now, we have separated out wadm types into the wadm-types
crate so they can be used separately without the full dependency tree of wadm as well as in places like wasm components. We also have a new Rust client (wadm-client
) available so people don't need to roll their own NATS requests anymore
New Contributors
- @ericgregory made their first contribution in #284
Full Changelog: v0.11.2...v0.12.0
v0.11.2
Full Changelog: v0.11.1...v0.11.2
v0.11.1
What's Changed
- chore(chart): Bumps chart to use latest released version by @thomastaylor312 in #267
- docs(README): Removes some issues that have been fixed or addressed by @thomastaylor312 in #268
- fix: Provider state handling from 0.82 by @brooksmtownsend in #270
Full Changelog: v0.11.0...v0.11.1
v0.11.0
release: v0.11.0
v0.11.0-alpha.4
release: v0.11.0-alpha.4
v0.11.0-alpha.3
Alpha 3 for v0.11
v0.11.0-alpha.2
What's Changed
- feat(model): support labels in manifest by @brooksmtownsend in #254
- chore/alpha 2 by @brooksmtownsend in #257
Full Changelog: v0.11.0-alpha.1...v0.11.0-alpha.2
v0.11.0-alpha.1
This is the first release of wadm that's designed to work with wasmCloud 1.0. Please note that configuration is only supported on links and by specifying the name, wadm doesn't have support for putting configuration yet.
What's Changed
- feat(*): subscribe to updated lattice event subjects by @connorsmith256 in #241
- feat: support TLS CA certificates when building a NATS client by @protochron in #243
- chore: Update the default OTLP HTTP port to match the current OTEL spec by @joonas in #242
- feat(events): support actor_scaled event by @brooksmtownsend in #238
- feat: Add helm chart for deploying wadm on Kubernetes by @joonas in #248
- Updates to wadm to support wasmCloud 1.0 by @brooksmtownsend in #247
- chore: bump to v0.11.0-alpha.1 by @brooksmtownsend in #255
Full Changelog: v0.10.0...v0.11.0-alpha.1
v0.10.0
What's Changed
- feat(status)!: rename compensating and ready status by @brooksmtownsend in #223
- chore: updated release github token by @brooksmtownsend in #227
- chore: addressed clippy warnings rust 1.74 by @brooksmtownsend in #226
- feat(model): max_concurrent instead of replicas by @brooksmtownsend in #221
- fix(scaler): remove backoff wrapper around link by @brooksmtownsend in #228
- chore: Update ahash version to bump zerocopy by @joonas in #229
- chore: Update wasm-bindgen version by @joonas in #232
- chore: Update serde_yaml version to bump unsafe-libyaml by @joonas in #230
- chore: Replace atty with std::io::IsTerminal by @joonas in #231
- feat(*)!: prevent querying inventory for new heartbeat by @brooksmtownsend in #233
- fix(scaler): always publish delete notification by @brooksmtownsend in #234
- release: v0.10.0-rc1 by @brooksmtownsend in #236
- fix(scaler): resolve possible linkdef loop by @brooksmtownsend in #237
- release: v0.10.0 by @brooksmtownsend in #240
Full Changelog: v0.9.1...v0.10.0