chore(deps): bump containerd-shim-wasm from 1.0.0-rc.1 to 1.0.0

[dependabot]

Bumps containerd-shim-wasm from 1.0.0-rc.1 to 1.0.0.

Release notes

Sourced from containerd-shim-wasm's releases.

containerd-shim-wasm/v1.0.0

Changed

• containerd_shim_wasm::sandbox::shim::Cli -> containerd_shim_wasm::sandbox::shim::Shim and it is no longer public, because this was not intended to be used by users of the crate.
• Breaking change: All methods in the Engine trait (except name and supported_layers_types) are now async. (#931)
• The Engine trait is now being split into Shim, Sandbox and Compiler traits. (#936)
• The container module is renamed to shim module. (#936)
• The Instance trait is moved to the containerd_shimkit crate, which has it's own changelog, version and README. (#930)
• Reorganized types, traits and macros in more meaningful modules. (#957)
• Config is now locally defined instead of re-exported, and doesn't expose the no_reaper or no_sub_reaper options. (#957)

Removed

• Removed the shim_main function. Use ShimCli::run trait method instead. (#944 and #943)
• The with_lease macro, otel module and instance_utils module are now private. (#929)
• The logging macros are removed. Now, the pod ID and container ID are unconditionally added to any logging coming from a sandbox process. (#953
• Removed from RuntimeContext the methods: platform, pod_id, and container_id. (#971)

Full Changelog: containerd/runwasi@containerd-shim-wasm/v0.10.0...containerd-shim-wasm/v1.0.0

Changelog

Sourced from containerd-shim-wasm's changelog.

Release Process

This document describes the steps to release a new version of the crate or wasi-demo-app images.

Table of Contents

1. Crate Release Process
   • Overview
   • Input Values for Release.yml
   • Crate Release Sequence
   • Release Steps
   • Local Development vs. Release
   • Verify signing
   • First time release of a crate
   • Release workflow summary
2. wasi-demo-app Release Process
   • Overview
   • Verify signing

Crate Release Process

Overview

To create a new release, either run the release.yml workflow as a workload_dispatch trigger through the GitHub UI, or via the following command substituting the proper values for crate and version.

gh workflow run release.yml -f dry_run=true -f crate=containerd-shim-wasm -f version=0.4.0

Input Values for Release.yml

• crate: [string] the name of the crate within the runwasi project. It should be a directory under ./crates.
• version: [string] the version of the crate to stamp, tag, and release (e.g., 1.0.0, 0.6.0-rc1)
• dry_run: [boolean] a flag that causes the workflow to run all step except ones that would tag or push artifacts.

Crate Release Sequence

Must release the creates in this order due to dependencies:

1. containerd-shimkit
2. containerd-shim-wasm
3. All runtime-related crates.

Release Steps

1. Open a PR to bump crate versions and dependency versions in Cargo.toml for that crate, and change the "Unreleased" section in the CHANGELOG.md to the new version.
2. PR can be merged after 2 LGTMs
3. Run the release workflow for the dependent crate. (e.g. containerd-shim-wasm/v0.2.0 where crate=containerd-shim-wasm and version=0.2.0)
4. Wait for the release workflow to complete
5. Manually verify the release on crates.io and on the GitHub releases page (See Verify signing section for more details on verifying the release on GitHub releases page.)
6. If this is the first time publishing this crate, see the First release of a crate section.

... (truncated)

Commits

• 5652bc9 chore(deps): bump wasmparser from 0.227.1 to 0.228.0 (#975)
• 1520da7 chore(deps): bump the patch group with 3 updates (#976)
• f4abcf0 containerd-shim-wasm: bump version to 1.0.0 (#977)
• 71355b8 Merge pull request #971 from jprendes/cleanup-wasicontext
• 1133476 update changelog
• 152fea3 Remove platform from contianerd client API
• 775d2b5 chore(deps): bump the patch group with 2 updates (#973)
• 663183d chore(deps): bump github/codeql-action from 3.28.14 to 3.28.15 (#972)
• cb4299b chore(deps): bump indexmap from 2.8.0 to 2.9.0 (#974)
• d24e9e6 delete setup-containerd.sh (#966)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.