! This version will be not published as "latest" because a 1.5.8 (latest) > 1.5.8 (current version). Publishing as "ci"

npm notice npm notice 📦 @well-known-components/[email protected] npm notice === Tarball Contents === npm notice 14B README.md npm notice 1.5kB dist/index.d.ts npm notice 1.3kB dist/index.d.ts.map npm notice 4.3kB dist/index.js npm notice 3.3kB dist/index.js.map npm notice 465B dist/localFetch.d.ts npm notice 300B dist/localFetch.d.ts.map npm notice 2.7kB dist/localFetch.js npm notice 1.1kB dist/localFetch.js.map npm notice 17.9kB dist/test-helpers.api.json npm notice 340B dist/tsdoc-metadata.json npm notice 1.2kB package.json npm notice === Tarball Details === npm notice name: @well-known-components/test-helpers npm notice version: 1.5.8 npm notice filename: @well-known-components/test-helpers-1.5.8.tgz npm notice package size: 6.8 kB npm notice unpacked size: 34.5 kB npm notice shasum: c6826fab2c1244f91a0bef809d29fecbff787fdf npm notice integrity: sha512-NewY/t2l4D6iG[...]FIv3ZLQyy1wdw== npm notice total files: 12 npm notice npm notice Publishing to https://registry.npmjs.org/ npm ERR! code E403 npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/@well-known-components%2ftest-helpers - You cannot publish over the previously published versions: 1.5.8. npm ERR! 403 In most cases, you or one of your dependencies are requesting npm ERR! 403 a package version that is forbidden by your security policy, or npm ERR! 403 on a server you do not have access to. npm ERR! A complete log of this run can be found in: npm ERR! /home/runner/.npm/_logs/2024-09-11T22_17_50_627Z-debug-0.log

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1, menduz/oddish-action@master. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/