release-notes-generator | release plugin to generate changelog content | DevOps library

I have this Angular library uploaded to a package registry that I created on Gitlab. I've already been able to upload my library successfully to this registry using the CI. I now want to implement semantic versionning to this library, but I'm not quite sure how to do it... The version of my library does not seem to update. Here is my current Gitlab CI config :

Here is the error log message:

[3:40:55 PM] [semantic-release] › ✖ The command "git push --dry-run --no-verify https://gitlab-ci-token:[secure]@[repository-url].git HEAD:main" failed with the error message remote: You are not allowed to upload code. fatal: unable to access 'https://gitlab-ci-token:[secure]@[repository-url]/': The requested URL returned error: 403.

I have a GITLAB_TOKEN set up in the repository settings with all the necessary permissions, but it seems it isn't even being used:

Here is my .releaserc.json config:

I have a C# solution containing a single project and multiple libraries using .Net 6. I'm using conventional commits (commitlint with husky) and want to use semantic-release to deploy the latest build as a ZIP file on Github based on the commit messages.

The setup I tried for C# projects:

• Install packages

.

What I want to do

Based on the FAQ

https://semantic-release.gitbook.io/semantic-release/support/faq#why-is-the-package.jsons-version-not-updated-in-my-repository

I want to update the package.json version number on a new release.

What I did

• Create a new empty private Github repository for an organization temp with a README.md and .gitignore for node
• Clone the repository
• Fix the first commit message via git rebase -i --root and change it to feat: initial commit
• Create a package.json with the content

I'm trying to use semantic-release to publish to a scoped private registry on gitlab but I keep getting error because it's trying to auth against the public registry instead the private one.

Here are my settings (with some things obscured)

package.json

We are using Azure Pipelines (azure-pipelines.yml) to automate ci/cd. Part of our configuration completes the versioning of our project for publishing to Azure Artifacts. We're also trying to configure this to update the existing version number in package.json without triggering a new pipeline in Azure DevOps.

This is the relevant section for our azure-pipelines.yml file:

Using @semantic-release I'd like to consider refactor changes for both, triggering a new release and write down in the CHANGELOG.md file.

So far, I've included refactor commits at "@semantic-release/commit-analyzer" so they are triggering a patch release:

I'm using semantic-release to automatically define the next version, update package.json and push to git. However, I'm facing a problem where it stop me from direct pushing to master.

I'm using GitLab.

my release.config.js

I have some logs outputted by semantic-release. I would like to get the next semantic version.

Here's some of the logs