Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for release v0.4.0 #105

Merged
merged 2 commits into from
Aug 16, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "bartholomew"
version = "0.3.0"
version = "0.4.0"
edition = "2021"
authors = ["Fermyon Engineering <engineering@fermyon.com>"]

Expand Down
2 changes: 1 addition & 1 deletion bart/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "bart"
version = "0.1.0"
version = "0.4.0"
edition = "2021"
authors = ["Fermyon Engineering <engineering@fermyon.com>"]

Expand Down
Binary file modified docs/modules/bartholomew.wasm
Binary file not shown.
2 changes: 1 addition & 1 deletion release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
To cut a release of Bartholomew, you will need to do the following:

1. Create a pull request that changes the version number for your new version (e.g. 1.2.2 becomes 1.2.3)
- `Cargo.toml` is the most important place to make this change
- `Cargo.toml` and `bart/Cargo.toml` are the most important places to make this change
- Check the docs for hard-coded version strings
2. Merge the PR created in #1 (Such PRs are still required to get approvals, so make sure you get signoff on the PR)
3. Create a new tag with a `v` and then the version number (`v1.2.3`)
Expand Down