[C]
By using the needs keyword, you create a sequential dependency. If the build job fails or is skipped, the publish-npm job will not run by default.
In a GitHub Actions workflow, a job with the needs keyword will run only if the jobs it needs complete successfully or are skipped without an error. By default, if a dependency fails, the dependent job (in this case, publish-npm) is automatically skipped.
To make the publish-npm job run even if the build job fails, you must use a conditional expression, such as if: always() or if: success() || failure().
[B, not A]
We see in the last line of code that an NPM token is used for authentication- Note:
When publishing a Node.js package using GitHub Actions, the primary differences between using the npm registry and GitHub Packages involve authentication methods, registry configuration, and package naming requirements.
Key Differences at a Glance
*-> Authentication .
For npm Registry
Requires a manually created npm token stored as a secret
For GitHub Packages
Can use the built-in GITHUB_TOKEN automatically provided by GitHub.
Reference:
https://blog.anoff.io/2020-07-private-npm-package-github
https://dev.to/gervaisamoah/introduction-to-github-actions-easy-guide-3p23

In GitHub Actions, environment variables can be defined at three different scopes: workflow, job, and step. Each scope determines the visibility and lifetime of the environment variable across the workflow execution.
Variables defined at the workflow scope are available to all jobs and steps within the workflow.
Variables defined at the job scope are available to all steps within a specific job.
Variables defined at the step scope are only available to the step in which they are defined. They are declared within a step and are not visible outside of that step.
Reference:
https://medium.com/@leroyleowdev/github-actions-ways-to-share-data-between-jobs-
4267ff9ac2ce

The metadata file that defines the main entry point for a custom GitHub Action is action.yml (or action.yaml).
This file, located in the root directory of your action's repository, uses YAML syntax and includes a runs key that specifies how the action is executed and which script is the main entry point.
Key fields in the action.yml file
name: The name of your action displayed in the GitHub Actions UI.
description: A short description of the action.
runs: This required key specifies the execution environment and the main entry point.
For a JavaScript action, the runs field includes using (e.g., node20) and main (e.g., index.js) to define the runtime and the primary script file.
For a Docker container action, the runs field includes using: 'docker' and image (e.g., 'Dockerfile') to point to the Docker build file or image.
inputs: Optional parameters that allow users to pass data to your action.
outputs: Optional output parameters that the action can produce for use by subsequent steps in a workflow.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax

Example: Using versioned actions
steps:
# Reference a specific commit
- uses: actions/checkout@8f4b7f84864484a7bf31766abe9204da3cbe65b3
*-> # Reference the major version of a release
- uses: actions/checkout@v4
# Reference a specific version
- uses: actions/[email protected]
# Reference a branch
- uses: actions/checkout@main
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax

Defining environment variables for a single workflow
To set a custom environment variable for a single workflow, you can define it using the env key in the workflow file. The scope of a custom variable set by this method is limited to the element in which it is defined. You can define variables that are scoped for:
[A] The entire workflow, by using env at the top level of the workflow file.
[E] The contents of a job within a workflow, by using jobs.<job_id>.env.
[F] A specific step within a job, by using jobs.<job_id>.steps[*].env.
Reference:
https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use- variables