ci: change test internal libwasmvm binary triggered only build PR #143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the trigger of the test of internal libwasmvm binaries.
This is always triggered before this PR, and this PR changes it triggered only PR by the libwasmvm build bot.
Description
wasmvm has 2 tests for PR for the main branch, before this PR.
An error is caused in CI when internal/api's libwasmvm is old, though we have a CI building libwasmvm binaries after the main branch is updated.
As a result, if PR publishers think that they leave building libwasmvm on CI after the merge, internal libwasmvm's test fails. (now we have this issue on #142)
To solve this, we change the trigger of the test of internal/api's libwasmvm binaries.
Types of changes
Checklist