Add GitHub actions for publishing crates. (#147)

* Add GitHub actions for publishing crates.

This commit adds a GitHub action (based on a similar one from Wasmtime) for
publishing the crates when new tags are created.

This also bumps the crate versions to 0.2.0, which will be the first versions
of the crates published.

* Add the `wit` tool to publishing.

The `wit` tool will also start at version 0.1.0.

* Add README to packages.

* Update .github/workflows/publish-to-crates-io.yml

Co-authored-by: Brian <[email protected]>

---------

Co-authored-by: Brian <[email protected]>

Author: peterhuene

.github/workflows/publish-to-crates-io.yml

@@ -0,0 +1,23 @@
+# The purpose of this workflow is to publish the workspace's crates
+# whenever a tag is created. This basically boils down to running
+# `scripts/publish.rs` at the right time.
+
+name: "Publish to crates.io"
+
+on:
+  push:
+    tags:
+    - 'v*'
+
+jobs:
+  publish:
+    if: github.repository == 'bytecodealliance/cargo-component'
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    - run: rustup update stable && rustup default stable
+    - run: |
+        rustc ci/publish.rs
+        ./publish publish
+      env:
+        CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}

Cargo.lock

@@ -6,9 +6,10 @@ edition = { workspace = true }
 authors = { workspace = true }
 license = { workspace = true }
 repository = { workspace = true }
+readme = "README.md"
 
 [workspace.package]
-version = "0.1.0"
+version = "0.2.0"
 edition = "2021"
 authors = ["Peter Huene <[email protected]>"]
 license = "Apache-2.0 WITH LLVM-exception"
@@ -59,8 +60,8 @@ members = ["crates/bindings", "crates/macro", "crates/core", "crates/wit"]
 exclude = ["target/tests"]
 
 [workspace.dependencies]
-cargo-component-core = { path = "crates/core", version = "0.1.0" }
-cargo-component-macro = { path = "crates/macro", version = "0.1.0" }
+cargo-component-core = { path = "crates/core", version = "0.2.0" }
+cargo-component-macro = { path = "crates/macro", version = "0.2.0" }
 warg-protocol = "0.1.0"
 warg-crypto = "0.1.0"
 warg-client = "0.1.0"

Cargo.toml

@@ -38,13 +38,9 @@ may cause build errors for existing component projects.
 To install the `cargo component` subcommand, run the following command:
 
 ```
-cargo install --git https://github.com/bytecodealliance/cargo-component --locked cargo-component
+cargo install cargo-component
 ```
 
-The [currently published crate](https://crates.io/crates/cargo-component)
-on crates.io is a nonfunctional placeholder and these instructions will be
-updated to install the crates.io package once a proper release is made.
-
 ## Motivation
 
 Today, developers that target WebAssembly typically compile a monolithic
@@ -295,9 +291,8 @@ for other IDEs.
 ## Contributing to `cargo component`
 
 `cargo component` is a [Bytecode Alliance](https://bytecodealliance.org/)
-project, and follows
-the Bytecode Alliance's [Code of Conduct](CODE_OF_CONDUCT.md) and
-[Organizational Code of Conduct](ORG_CODE_OF_CONDUCT.md).
+project, and follows the Bytecode Alliance's [Code of Conduct](CODE_OF_CONDUCT.md)
+and [Organizational Code of Conduct](ORG_CODE_OF_CONDUCT.md).
 
 ### Getting the Code
 
@@ -333,14 +328,10 @@ command. This is checked on CI.
 The CI for the `cargo component` repository is relatively significant. It tests
 changes on Windows, macOS, and Linux.
 
-It also performs a "dry run" of the release process to ensure that release
-binaries can be built and are ready to be published (_coming soon_).
-
-### Publishing (_coming soon_)
+### Publishing
 
 Publication of this crate is entirely automated via CI. A publish happens
 whenever a tag is pushed to the repository, so to publish a new version you'll
-want to make a PR that bumps the version numbers (see the `bump.rs` scripts in
-the root of the repository), merge the PR, then tag the PR and push the tag.
-That should trigger all that's necessary to publish all the crates and binaries
-to crates.io.
+want to make a PR that bumps the version numbers (see the `ci/publish.rs` 
+script), merge the PR, then tag the PR and push the tag. That should trigger 
+all that's necessary to publish all the crates and binaries to crates.io.