Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Passing enviornment variables to the script

Open
#160 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, shell
Domain
release

Research direction

Start with the publishCmd configuration and the scripts/publish.js entry point to trace how the command receives environment variables. Reproduce the reported configuration, then verify that the selected variable reaches scripts/publish.js when the publish command runs.

Written by the indexing model from the issue text.

Description

My "publishCmd" script needs environment variables to be set to run properly.
How could I pass them to the script?

I've tried the code below but with no success:

"@semantic-release/exec",
{
    "publishCmd": "node ./scripts/publish.js ${env.CI_ENVIRONMENT_VARIABLE}"
}
Dominant language
JavaScript
Stars
164
Forks
28
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-release/exec

All issues in semantic-release/exec

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.