Possible to use this in a rust project?

[gooseops]

I have a rust project that I'd like to use semantic-release for. I just want the releasing changelog, tagging, and releasing funcitonality. I don't need the npm package publish, obviously. I can't seem to get it to run because it's expecting to publish packages.

Can I disable this feature? If so, can someone point me to the specific docs on this??

Here is the Actions error I am getting (probably working as expected)

npm warn exec The following package was not found and will be installed: semantic-release@24.0.0
npm warn deprecated read-pkg-up@11.0.0: Renamed to read-package-up
[1:32:1[7](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:8) PM] [semantic-release] › ℹ  Running semantic-release version 24.0.0
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[1:32:17 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[1:32:1[8](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:9) PM] [semantic-release] › ✔  Run automated release from branch main on repository https://github.com/gooseops/hello_world
[1:32:1[9](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:10) PM] [semantic-release] › ✔  Allowed to push to the Git repository
[1:32:19 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/npm"
[1:32:19 PM] [semantic-release] [@semantic-release/npm] › ℹ  Verify authentication for registry https://registry.npmjs.org/
[1:32:19 PM] [semantic-release] › ✘  Failed step "verifyConditions" of plugin "@semantic-release/npm"
[1:32:19 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/github"
[1:32:19 PM] [semantic-release] [@semantic-release/github] › ℹ  Verify GitHub authentication (https://api.github.com)
[1:32:19 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/github"
[1:32:19 PM] [semantic-release] › ℹ  Start step "fail" of plugin "@semantic-release/github"
[1:32:20 PM] [semantic-release] [@semantic-release/github] › ℹ  Created issue #6: https://github.com/gooseops/hello_world/issues/6.
[1:32:20 PM] [semantic-release] › ✔  Completed step "fail" of plugin "@semantic-release/github"
[1:32:20 PM] [semantic-release] › ✘  ENONPMTOKEN No npm token specified.
An npm token (https://github.com/semantic-release/npm/blob/master/README.md#npm-registry-authentication) must be created and set in the NPM_TOKEN environment variable on your CI environment.
Please make sure to create an npm token (https://docs.npmjs.com/getting-started/working_with_tokens#how-to-create-new-tokens) and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.
AggregateError: 
    SemanticReleaseError: No npm token specified.
        at default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/lib/get-error.js:7:[10](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:11))
        at default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/lib/set-npmrc-auth.js:35:31)
        at default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/lib/verify-auth.js:17:9)
        at verifyConditions (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/index.js:33:13)
        at async validator (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/lib/plugins/normalize.js:36:24)
        at async file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/lib/plugins/pipeline.js:38:36
        at async Promise.all (index 0)
        at async next (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/p-reduce/index.js:15:44)
    at file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/lib/plugins/pipeline.js:55:13
    at async pluginsConfigAccumulator.<computed> [as verifyConditions] (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/lib/plugins/index.js:87:[11](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:12))
    at async run (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/index.js:106:3)
    at async Module.default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/index.js:278:22)
    at async default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/cli.js:55:5) {
  errors: [
    SemanticReleaseError: No npm token specified.
        at default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/lib/get-error.js:7:10)
        at default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/lib/set-npmrc-auth.js:35:31)
        at default (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/lib/verify-auth.js:17:9)
        at verifyConditions (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/@semantic-release/npm/index.js:33:[13](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:14))
        at async validator (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/lib/plugins/normalize.js:36:24)
        at async file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/semantic-release/lib/plugins/pipeline.js:38:36
        at async Promise.all (index 0)
        at async next (file:///home/runner/.npm/_npx/cdf31b77322f1d44/node_modules/p-reduce/index.js:[15](https://github.com/gooseops/hello_world/actions/runs/9614486065/job/26519397890#step:4:16):44) {
      code: 'ENONPMTOKEN',
      details: 'An [npm token](https://github.com/semantic-release/npm/blob/master/README.md#npm-registry-authentication) must be created and set in the `NPM_TOKEN` environment variable on your CI environment.\n' +
        '\n' +
        'Please make sure to create an [npm token](https://docs.npmjs.com/getting-started/working_with_tokens#how-to-create-new-tokens) and to set it in the `NPM_TOKEN` environment variable on your CI environment. The token must allow to publish to the registry `https://registry.npmjs.org/`.',
      semanticRelease: true,
      pluginName: '@semantic-release/npm'
    }
  ]
}
Error: Process completed with exit code 1.

[gooseops]

Found it.
FAQ

[travi]

be sure to also check out our list of community plugins: https://semantic-release.gitbook.io/semantic-release/extending/plugins-list#community-plugins. one is listed there for use with cargo

[gooseops]

be sure to also check out our list of community plugins: https://semantic-release.gitbook.io/semantic-release/extending/plugins-list#community-plugins. one is listed there for use with cargo

Thanks!

[travi]

decided to add a link to make that more findable. thanks for closing the loop with where you found the info you did