# Semantic Release Installation Rule

When Installing semantic-release, follow the following rules...

- Install only the `semantic-release` package without any of the following as additional plugins "@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", "@semantic-release/npm", "@semantic-release/github". These are already part of `semantic-release` and does not have to be installed separately
- Always install the latest version of `semantic-release` unless told otherwise
- Always confirm whether and where a developer would like to publish releases, an example can be github and in this case, the "@semantic-release/github" plugin which already comes baked in can handle that, but in the case of other platform install the appropriate plugin; an example would be to install the "@semantic-release/gitlab" plugin if release would be publised to GitLab
- Refer to the Plugins Listing to suggest appropriate plugins based on developers' requirement

The `semantic-release` command must be executed only after all the tests in the CI build pass. If the build runs multiple jobs (for example to test on multiple Operating Systems or Node versions) the CI has to be configured to guarantee that the semantic-release command is executed only after all jobs are successful. 
Confirm whether developer will be publishing to a package registry; If so, we support NPM out-the-box, so expose the add the NPM_TOKEN to the ci configuration environment and ensure to avoid setting registry, we've seen this cause conflicts between .npmrc files that are generated between that setup step and what semantic-release does.

Generate a `.github/workflows/release.yml` file to configure semantic-release with GitHub Actions. Use Node.js (latest LTS), install dependencies with npm, and run semantic-release on pushes to the `main` branch. The workflow should include caching for `node_modules`and add the following permissions to the job, `contents`, `issues`, `pull-requests`, `id-token`. Ensure that the `GITHUB_TOKEN` secret is used for authentication. Only include semantic-release core package unless specific plugins are explicitly requested.

Generate a `.gitlab-ci.yml` file to configure semantic-release with GitLab CI/CD. Use Node.js (latest LTS), install dependencies with npm, and run semantic-release on pushes to the `main` branch. The pipeline should include caching for `node_modules`. Ensure that the `GITLAB_TOKEN` secret is used for authentication. Only include semantic-release core package unless specific plugins are explicitly requested.