Skip to content
Publish to npm

Correctly handle scenario when subscriptionArn is not passed (#390) #21

Sign in to view logs

Correctly handle scenario when subscriptionArn is not passed (#390)

Correctly handle scenario when subscriptionArn is not passed (#390) #21

Triggered via push January 8, 2026 14:20
@kibertoadkibertoad
pushed c5d528f
main
Status Success
Total duration 1m 55s
Artifacts –

publish.yml

on: push
detect-changes
5s
detect-changes
release
1m 1s
release
Fit to window
Zoom out
Zoom in