This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Lock file maintenance

Pending Branch Automerge

These updates await pending status checks before automerging. Click on a checkbox to abort the branch automerge, and create a PR instead.

• Update dependency prettier to v3.3.1

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency got to v14.4.0
• Update dependency commander to v12
• Update dependency date-fns to v3
• Update dependency ink to v5
• Update dependency jscpd to v4
• Update dependency p-queue to v8
• Update eslint packages (major) (eslint, eslint-plugin-ava)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

please help

/Users/peter/Desktop>glpd -d https://gitlab.com 4572912 glpat-yY1n7xCW69c23123Sgihr
Missing or invalid arguments

🚨 The automated release from the main branch failed. 🚨

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

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 resolve 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 is 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, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-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 📦🚀

I want to not delete pipelines associated with tags.

The inverse list of /projects/:id/pipelines?scope=tags

The branches scope is probably close enough: /projects/:id/pipelines?scope=branches

Can I do that without hacking at the module code?

0 days in the config:

module.exports = {
    gitlabUrl: 'https://gitlab.com',
    projectId: '1',
    accessToken: 'GLPAT_xyz',
    days: 0,
    trace: false,
};

always results in 0 pipelines found. Any pipelines less than a day old cannot be deleted.

It seems a small change in gitlab.tx isOlderThanDays would allow this.

I tried to run glpd without a config file and it ended up dying silently with:

Missing or invalid arguments

Doing a console.log on the arguments showed:

/ # /usr/local/bin/glpd --days=800 https://gitlab.com 1337 hahahaha
Err {
  variant: 'Err',
  error: "ENOENT: no such file or directory, open '/glpd.config.js'"
}

So maybe we should state that the config file at glpd.config.js in cwd is necessary or make it optional. What do you think?

Hello there!

My name is Ana. I noted that you use the mutation testing tool StrykerJS in the project.
I am a postdoctoral researcher at the University of Seville (Spain), and my colleagues and I are studying how mutation testing tools are used in practice. With this aim in mind, we have analysed over 3,500 public GitHub repositories using mutation testing tools, including yours! This work has recently been published in a journal paper available at https://link.springer.com/content/pdf/10.1007/s10664-022-10177-8.pdf.

To complete this study, we are asking for your help to understand better how mutation testing is used in practice, please! We would be extremely grateful if you could contribute to this study by answering a brief survey of 21 simple questions (no more than 6 minutes). This is the link to the questionnaire https://forms.gle/FvXNrimWAsJYC1zB9 .

We apologize if you have already received message multiple times or if you have already had the opportunity to complete the survey. If you have already shared your feedback, we want to convey our appreciation, kindly disregard this message, and please accept our apologies for any inconvenience.

Drop me an e-mail if you have any questions or comments ([email protected]). Thank you very much in advance!!