You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(release): satisfy npm provenance so packages actually publish (#18)
The publish run went green while every npm publish silently failed with
E422: provenance validation requires repository.url to match the repo
the workflow runs from, and the generated platform/meta manifests had no
repository field at all (the sdk and plugin manifests likewise), while
the root and launcher manifests pointed at the wrong-case repo path.
- stamp repository into the generated platform and wrapper manifests
- add repository to the sdk and plugin packages
- normalize existing repository URLs to the canonical lowercase path
- release orchestration now records per-section failures and exits
non-zero, so a green publish run means packages really shipped
0 commit comments