-
Notifications
You must be signed in to change notification settings - Fork 593
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
js: replace wasm-api library scope #8357
js: replace wasm-api library scope #8357
Conversation
@r-vasquez I updated the release workflow to update node to the nearest lts version. |
Update wasm-api npm library from @vectorizedio/wasm-api to @redpanda-data/wasm-api. This change moves wasm-api to the Redpanda's npm organisation.
update version of nodejs to 14.x.x, version 12 is not maintaiened anymore. update the actions trigger, even should only trigger on some specific tag push events.
fc2d310
to
3848387
Compare
thanks @sago2k8 , token has been updated |
@ivotron Can we merge then, right? |
yes, though the bump of node version might break the workflow. since it doesn't run on PRs, only on tags, this will be tested when we release. but let's do it and if it breaks we fix quickly |
Update wasm-api npm library from @vectorizedio/wasm-api to @redpanda-data/wasm-api.
This change moves wasm-api to the Redpanda's npm organisation.
Backports Required
UX Changes
Replace the wasm npm library from
@vectorizedio/wasm-api
to@redpanda-data/wasm-api
.Release Notes
fixes https://github.com/redpanda-data/devprod/issues/430