Stream: git-wasmtime

Topic: wasmtime / issue #3489 Release Wasmtime 0.31.0


view this post on Zulip Wasmtime GitHub notifications bot (Oct 28 2021 at 21:58):

alexcrichton commented on issue #3489:

Ok I've updated the release notes here for a scheduled release of tomorrow. If there are no objections by then I'll merge this tomorrow morning to test out the further stages of the automation.

view this post on Zulip Wasmtime GitHub notifications bot (Oct 28 2021 at 22:13):

github-actions[bot] commented on issue #3489:

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "cranelift", "cranelift:area:peepmatic", "cranelift:meta", "cranelift:module", "cranelift:wasm", "wasmtime:docs"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Oct 29 2021 at 14:17):

bjorn3 commented on issue #3489:

https://github.com/bytecodealliance/wasmtime/runs/4047534764?check_suite_focus=true

    Updating crates.io index
   Packaging wiggle v0.31.0 (/home/runner/work/wasmtime/wasmtime/crates/wiggle)
   Uploading wiggle v0.31.0 (/home/runner/work/wasmtime/wasmtime/crates/wiggle)
error: failed to publish to registry at https://crates.io

Caused by:
  failed to get a 200 OK response, got 500
  headers:
    HTTP/2 500
    content-length: 21
    server: nginx
    date: Fri, 29 Oct 2021 14:16:04 GMT
    strict-transport-security: max-age=31536000
    via: 1.1 vegur, 1.1 966a4e45512437c14125c564c492a2d6.cloudfront.net (CloudFront)
    x-cache: Error from cloudfront
    x-amz-cf-pop: IAD50-C2
    x-amz-cf-id: aVA1jAVDqpqayoYKdAOYEo80cFKddWvR1I1LCq-2-M7GP7b_mjLmjg==

  body:
  Internal Server Error
FAIL: failed to publish `wasi-cap-std-sync`: exit status: 101

It does continue with the publishing process though.

view this post on Zulip Wasmtime GitHub notifications bot (Oct 29 2021 at 14:18):

bjorn3 commented on issue #3489:

Publishing wasmtime-cli failed too:

    Updating crates.io index
   Packaging wasmtime-cli v0.31.0 (/home/runner/work/wasmtime/wasmtime)
error: failed to prepare local package for uploading

Caused by:
  failed to select a version for the requirement `wasmtime = "^0.31.0"`
  candidate versions found which didn't match: 0.30.0, 0.29.0, 0.28.0, ...
  location searched: crates.io index
  required by package `wasmtime-cli v0.31.0 (/home/runner/work/wasmtime/wasmtime)`
FAIL: failed to publish `wasmtime-cli`: exit status: 101
1 crates failed to publish, waiting for a bit to retry
    Updating crates.io index
   Packaging wasmtime-cli v0.31.0 (/home/runner/work/wasmtime/wasmtime)
error: failed to prepare local package for uploading

Caused by:
  failed to select a version for the requirement `wasmtime-wasi-crypto = "^0.31.0"`
  candidate versions found which didn't match: 0.30.0, 0.29.0, 0.28.0, ...
  location searched: crates.io index
  required by package `wasmtime-cli v0.31.0 (/home/runner/work/wasmtime/wasmtime)`
FAIL: failed to publish `wasmtime-cli`: exit status: 101

view this post on Zulip Wasmtime GitHub notifications bot (Oct 29 2021 at 14:24):

alexcrichton commented on issue #3489:

Wow I think this worked on the first try! Hurray!

@bjorn3 that's expected, if you read further you'll see the retry happening until it succeeds.


Last updated: Dec 23 2024 at 12:05 UTC