Skip to content

fix: cleaned up editor configs. added job schema to package export #42

fix: cleaned up editor configs. added job schema to package export

fix: cleaned up editor configs. added job schema to package export #42

Triggered via push July 10, 2024 12:06
Status Failure
Total duration 3m 43s
Artifacts

main.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Release
Error: Command failed with exit code 1: npm publish /home/runner/work/resume-schema/resume-schema --userconfig /tmp/a69ae1704b326fbad77c0c51285ec4a5/.npmrc --tag latest --registry https://registry.npmjs.org/ npm notice npm notice 📦 @jsonresume/[email protected] npm notice === Tarball Contents === npm notice 1.1kB LICENSE.md npm notice 3.8kB README.md npm notice 4.2kB job-schema.json npm notice 985B package.json npm notice 1.6kB sample.job.json npm notice 5.0kB sample.resume.json npm notice 15.0kB schema.json npm notice 451B validator.js npm notice === Tarball Details === npm notice name: @jsonresume/schema npm notice version: 1.1.1 npm notice filename: jsonresume-schema-1.1.1.tgz npm notice package size: 8.2 kB npm notice unpacked size: 32.1 kB npm notice shasum: 349e40a0d8e93e2617ca9113b8d1fc5bd64eb510 npm notice integrity: sha512-DLDoCtNuAEqi/[...]NQ0zmXQxQPdHg== npm notice total files: 8 npm notice npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access npm ERR! code E403 npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/@jsonresume%2fschema - You cannot publish over the previously published versions: 1.1.1. 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: /home/runner/.npm/_logs/2024-07-10T12_10_20_546Z-debug-0.log
Test on Node.js 18
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Test on Node.js 18
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on Node.js 20
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Test on Node.js 20
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Release
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/