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

chore(ci) bump TinyGo #519

Merged
merged 1 commit into from
Feb 29, 2024
Merged

chore(ci) bump TinyGo #519

merged 1 commit into from
Feb 29, 2024

Conversation

thibaultcha
Copy link
Member

@thibaultcha thibaultcha commented Feb 28, 2024

No description provided.

@thibaultcha thibaultcha force-pushed the chore/bump-go-sdk branch 2 times, most recently from 408680c to 25287dd Compare February 28, 2024 22:40
@thibaultcha thibaultcha changed the title chore(deps) bump proxy-wasm-go-sdk to an upstream commit chore(ci) bump TinyGo Feb 28, 2024
Copy link

codecov bot commented Feb 28, 2024

Codecov Report

Merging #519 (dd24406) into main (da5816e) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff              @@
##                main        #519   +/-   ##
=============================================
  Coverage   90.01315%   90.01315%           
=============================================
  Files             46          46           
  Lines           9883        9883           
=============================================
  Hits            8896        8896           
  Misses           987         987           
Flag Coverage Δ
unit 90.07941% <ø> (ø)
valgrind 77.84173% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@thibaultcha thibaultcha merged commit f59bed4 into main Feb 29, 2024
37 checks passed
@thibaultcha thibaultcha deleted the chore/bump-go-sdk branch February 29, 2024 15:56
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.

1 participant