GH Release and NPM Publish

add operator image for operator column #341

Triggered via push January 24, 2025 14:04

dskvr

pushed bf58876

Status Failure

Total duration 9m 41s

Artifacts 1

publish-package.yml

on: push

build

4m 52s

Matrix: publish

Annotations

17 errors and 34 warnings

publish (nocap-ssl-adapter-default)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (nocap-websocket-browser-adapter-default)

PackageJsonReadError: Could not read package.json at /package.json ENOENT: no such file or directory, open '/package.json'

publish (nocap-info-adapter-default)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (nocap-dns-adapter-default)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (nocap-geo-adapter-default)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (nocap-websocket-adapter-default)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (auditor)

InvalidPackageVersionError: Package version must be a valid semantic version, got "undefined"

publish (memory-relay)

NpmCallError: Call to "npm publish" exited with non-zero exit code 1 npm warn publish npm auto-corrected some errors in your package.json when publishing. Please run "npm pkg fix" to address these errors. npm warn publish errors corrected: npm warn publish "repository" was changed from a string to an object npm warn publish "repository.url" was normalized to "git+https://github.com/sandwichfarm/nostr-watch.git" npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access npm error code E404 npm error 404 Not Found - PUT https://registry.npmjs.org/@nostrwatch%2fmemory-relay - Not found npm error 404 npm error 404 '@nostrwatch/[email protected]' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-01-24T14_10_42_267Z-debug-0.log

publish (schemata)

NpmCallError: Call to "npm publish" exited with non-zero exit code 1 npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access npm error code E404 npm error 404 Not Found - PUT https://registry.npmjs.org/@nostrwatch%2fschemata - Not found npm error 404 npm error 404 '@nostrwatch/[email protected]' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-01-24T14_10_44_973Z-debug-0.log

publish (route66/adapters/cache/NostrSqliteAdapter)

PackageJsonReadError: Could not read package.json at /package.json ENOENT: no such file or directory, open '/package.json'

publish (route66/adapters/websocket/NostrToolsAdapter)

PackageJsonReadError: Could not read package.json at /package.json ENOENT: no such file or directory, open '/package.json'

publish (nocap-every-adapter-default)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (schemata-js-ajv)

NpmCallError: Call to "npm publish" exited with non-zero exit code 1 npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access npm error code E404 npm error 404 Not Found - PUT https://registry.npmjs.org/@nostrwatch%2fschemata-js-ajv - Not found npm error 404 npm error 404 '@nostrwatch/[email protected]' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-01-24T14_10_47_770Z-debug-0.log

publish (nostrings)

Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

publish (route66)

NpmCallError: Call to "npm publish" exited with non-zero exit code 1 npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access npm error code E404 npm error 404 Not Found - PUT https://registry.npmjs.org/@nostrwatch%2froute66 - Not found npm error 404 npm error 404 '@nostrwatch/[email protected]' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-01-24T14_10_49_920Z-debug-0.log

publish (nocap)

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

publish (nocap)

The operation was canceled.

build

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

build