🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Describe the bug
[ERROR] Cannot find module '~/utils/params' in NestJS application.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 Home Version 10.0.19044 Build 19044
• Browser: Chrome 112.0.5615.138 (Official Build) (64-bit)

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
I installed all versions from the latest to the 3.3.3. Same error. Using NestJS, TypeScript, pnpm. Tried installing dependencies with pnpm install --shamefully-hoist.

Describe the bug
Link to the OOP/POO library points to this library.

To Reproduce
Steps to reproduce the behavior:

1. Go to main repository page
2. Hover over the link of "because the official version in Transbank Developers is in POO, and POO sucks..."

Expected behavior
The link pointing to https://github.com/TransbankDevelopers/transbank-sdk-nodejs which is the OOP one.

Actual behavior
Link points to https://github.com/42devs/transbank-sdk-node/tree/main the FP one.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
If I'm being confused, ignore this issue please. I'm just trying to help someone with webpay.cl, and I'm discovering this library for first time. I am a big OOP advocate, but thanks to Vue 3, I'm starting to love FP more, but I still use OOP in NestJS and TypeScript decorators.

Wishing you all health, peace, and success. 🔥🤝😍☕

Hey Nicolas,

I am trying to use your package to implement transbank for nodejs,
I am getting this error when I am running your package in RunKit or locally, I have tried few things to fix it but they didn't work. Any idea what I can do to fix this

This is the code I wrote to call create function
var transbankSdkNode = require("transbank-sdk-node")
var transaction = new transbankSdkNode.Transaction(
"test")
transaction.create()

Create normal mall-type transaction methods, in addition to updating documentation

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://x-access-token:[secure]@github.com/42devs/transbank-sdk-node.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀