fix: regenerate 0.2 WIT docs and relock deps #151
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Roman Volosatovs <[email protected]>
Signed-off-by: Roman Volosatovs <[email protected]>
rvolosatovs
changed the title
rvolosatovs
changed the title
This was referenced Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes CI, which was broken by #150
FYI: PRs from bots (like GitHub Action) do not trigger CI runs and instead a dedicated bot user should be used (like one created via a GitHub App e.g. in https://github.com/rvolosatovs/nix-flake-update-action/blob/7249aa67d87e2a195c376fe34c230af0862a9900/action.yml#L66-L129, using https://github.com/actions/create-github-app-token which creates PRs like bytecodealliance/wrpc#643)