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

Fix push tag workflow #5082

Merged
merged 1 commit into from
Oct 20, 2022
Merged

Conversation

alexcrichton
Copy link
Member

This commit fixes the push-tag.yml workflow to work with the new Cargo.toml manifest since workspace inheritance was added. This additionally fixes some warnings coming up on CI about our usage of deprecated features on github actions.

This commit fixes the `push-tag.yml` workflow to work with the new
`Cargo.toml` manifest since workspace inheritance was added. This
additionally fixes some warnings coming up on CI about our usage of
deprecated features on github actions.
@alexcrichton alexcrichton enabled auto-merge (squash) October 20, 2022 18:55
@alexcrichton alexcrichton merged commit 0959f90 into bytecodealliance:main Oct 20, 2022
@alexcrichton alexcrichton deleted the fix-push-tags branch October 20, 2022 20:32
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Oct 26, 2022
This commit fixes the `push-tag.yml` workflow to work with the new
`Cargo.toml` manifest since workspace inheritance was added. This
additionally fixes some warnings coming up on CI about our usage of
deprecated features on github actions.
alexcrichton added a commit that referenced this pull request Oct 26, 2022
* Fix push tag workflow (#5082)

This commit fixes the `push-tag.yml` workflow to work with the new
`Cargo.toml` manifest since workspace inheritance was added. This
additionally fixes some warnings coming up on CI about our usage of
deprecated features on github actions.

* Reduce warnings on CI from GitHub Actions (#5083)

* Upgrade our github actions to "node16"

Each github actions run has a lot of warnings about using node12 so this
upgrades our repository to using node16. I'm hoping no other changes are
needed and I suspect other actions we're using are on node12 and will
need further updates, but this should help pin down what's remaining.

* Update `actions/checkout` workflow to `v3`

* Update to `actions/cache@v3`

* Update to `actions/upload-artifact@v3`

* Drop usage of `actions-rs/toolchain`

* Update to `actions/setup-python@v4`

* Update mdbook version

* Add `package-lock.json` for `github-release` action (#5091)

A local github action we have has been broken for about a month now
meaning that the `dev` tag isn't getting updated or getting new
releases. This appears to be due to the publication of new versions of
these dependencies which are running into issues using one another. I
think I've figured out versions that work and have added a
`package-lock.json` to ensure we keep using the same versions.

* More fixes for publish action (#5110)

Looks like #5091 wasn't enough and some of the APIs needed updating with
changes made in the meantime. I've updated the action here and
additionally made a separate change where the release isn't continually
created and deleted but instead left alone and only the tag is updated.
This should work for the `dev` release and avoids deleting/recreating on
each PR, sending out notifications for new releases.

* Add missing `Win32_Foundation` feature

This is necessary for the `wasmtime-runtime` crate to compile on Windows.

* Add a note for the 2.0.1 release

* Remove rayon dependency of cranelift-isle (#5101)

Using rayon adds a lot of dependencies to Cranelift. The total
unparallelized time the code that uses rayon takes is less than half a
second and it runs at compile time, so there is pretty much no benefit
to parallelizing it.

* Add a note about rayon removal

Co-authored-by: Christopher Serr <[email protected]>
Co-authored-by: bjorn3 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants