feat: new updated version of the multi-semantic-release lib

fix: fixed all eslint and prettier error, added new tests

feat: added github pipelines

fix: file filter

fix: added missing pnpm version into package.json

fix: fixed wrong export and found package audits

fix: fixed package.json to use the correct version for chai

fix: fixed clean-path on windows

fix: fixed node version and change testTimeout

fix: validate package.json

test: debug

test: debug

test: fix more windows paths

test: fix more windows paths

style: clean up

fix: windows is not supported

fix: added latest node version

.czrc

@@ -0,0 +1,4 @@
+{
+  "path": "cz-conventional-changelog"
+}
+

.editorconfig

@@ -0,0 +1,14 @@
+# https://EditorConfig.org
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 4
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.mdx]
+insert_final_newline = false

.eslintignore

@@ -1,2 +1,9 @@
-/node_modules/
-/coverage/
+node_modules
+vitest.config.ts
+.prettierrc.cjs
+_meta.*.json
+
+coverage
+__fixtures__
+
+.github/ISSUE_TEMPLATE

.eslintrc.cjs

@@ -0,0 +1,70 @@
+// eslint-disable-next-line import/no-commonjs
+const { defineConfig } = require("@anolilab/eslint-config/define-config");
+// eslint-disable-next-line import/no-commonjs
+const globals = require("@anolilab/eslint-config/globals");
+
+/** @ts-check */
+module.exports = defineConfig({
+    env: {
+        // Your environments (which contains several predefined global variables)
+        // Most environments are loaded automatically if our rules are added
+    },
+    extends: ["@anolilab/eslint-config"],
+    globals: {
+        ...globals.es2021,
+        // Your global variables (setting to false means it's not allowed to be reassigned)
+        // myGlobal: false
+    },
+    ignorePatterns: ["!**/*"],
+    overrides: [
+        {
+            files: ["**/*.js", "**/*.jsx", "**/*.mjs", "**/*.cjs"],
+            // Set parserOptions.project for the project to allow TypeScript to create the type-checker behind the scenes when we run linting
+            parserOptions: {},
+            rules: {},
+        },
+        {
+            files: ["**/*.ts", "**/*.tsx", "**/*.mts", "**/*.cts", "**/*.js", "**/*.jsx"],
+            // Set parserOptions.project for the project to allow TypeScript to create the type-checker behind the scenes when we run linting
+            parserOptions: {},
+            rules: {},
+        },
+        {
+            files: ["**/*.ts", "**/*.tsx", "**/*.mts", "**/*.cts"],
+            // Set parserOptions.project for the project to allow TypeScript to create the type-checker behind the scenes when we run linting
+            parserOptions: {},
+            rules: {
+                "security/detect-object-injection": "off",
+            },
+        },
+        {
+            files: ["**/*.test.js"],
+            rules: {
+                "security/detect-non-literal-fs-filename": "off",
+            },
+        },
+        {
+            files: ["**/*.js"],
+            rules: {
+                "func-style": "off",
+                "no-underscore-dangle": "off",
+            },
+        },
+        {
+            files: ["**/*.mdx"],
+            rules: {
+                "jsx-a11y/anchor-has-content": "off",
+                // @see https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/issues/917
+                "jsx-a11y/heading-has-content": "off",
+            },
+        },
+    ],
+    parserOptions: {
+        ecmaVersion: 2021,
+        sourceType: "module",
+    },
+    root: true,
+    rules: {
+        // Customize your rules
+    },
+});

.github/CODEOWNERS

@@ -0,0 +1 @@
+*               @prisis

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+-   Demonstrating empathy and kindness toward other people
+-   Being respectful of differing opinions, viewpoints, and experiences
+-   Giving and gracefully accepting constructive feedback
+-   Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+-   Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+-   The use of sexualized language or imagery, and sexual attention or
+    advances of any kind
+-   Trolling, insulting or derogatory comments, and personal or political attacks
+-   Public or private harassment
+-   Publishing others' private information, such as a physical or email
+    address, without their explicit permission
+-   Other conduct which could reasonably be considered inappropriate in a
+    professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: "prisis"

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,97 @@
+name: "\U0001F41E Bug report"
+description: "Report an issue"
+labels: ["s: pending triage", "c: bug"]
+body:
+    - type: "markdown"
+      attributes:
+          value: |
+              Thanks for taking the time to fill out this bug report!
+
+    - type: "checkboxes"
+      id: "checkboxes"
+      attributes:
+          label: "Pre-Checks"
+          description: "Before submitting the issue, please make sure you do the following"
+          options:
+              - label: "Follow our [Code of Conduct](https://github.com/anolilab/multi-semantic-release/blob/main/.github/CODE_OF_CONDUCT.md)."
+                required: true
+              - label: "Read the [Contributing Guidelines](https://github.com/anolilab/multi-semantic-release/blob/main/.github/CONTRIBUTING.md)."
+                required: true
+              - label: "Check that there isn't [already an issue](https://github.com/anolilab/multi-semantic-release/issues) that reports the same bug to avoid creating a duplicate."
+                required: true
+              - label: "Make sure this is a Visulima issue and not related to a combination with another package."
+                required: true
+              - label: "Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/anolilab/multi-semantic-release/discussions)."
+                required: true
+              - label: "The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug."
+                required: true
+              - label: "I am willing to provide a PR."
+
+    - type: "textarea"
+      id: "bug-description"
+      attributes:
+          label: "Describe the bug"
+          description: "A clear and concise description of what the bug is."
+          placeholder: "I am doing ... What I expect is ... What actually happening is ..."
+      validations:
+          required: true
+
+    - type: "textarea"
+      id: "reproduction"
+      attributes:
+          label: "Minimal reproduction code"
+          description: |
+              An URL to some git repository or gist that reproduces this issue. [Wtf is a minimum reproduction?](https://jmcdo29.github.io/wtf-is-a-minimum-reproduction)
+              Alternatively you could write the code sample directly here with [markdown support.](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)
+          placeholder: "https://github.com/... or ``` code ```"
+
+    - type: "textarea"
+      id: "additional-context"
+      attributes:
+          label: "Additional Context"
+          description: |
+              Anything else relevant?
+              **Tip:** You can attach images, recordings or log files by clicking this area to highlight it and then dragging files in.
+
+    - type: "textarea"
+      id: "environment-info"
+      attributes:
+          label: "Environment Info"
+          description: "Output of `npx envinfo --system --npmPackages '@anolilab/*' --binaries --browsers`"
+          render: "shell"
+          placeholder: |
+              System:
+                OS: _
+                CPU: _
+                Memory: _ / _
+                Container: Yes/No
+                Shell: _
+              Binaries:
+                Node: _ - /usr/bin/node
+                Yarn: _ - /usr/bin/yarn
+                npm: _ - /usr/bin/npm
+              npmPackages:
+                @anolilab/*: _ => _
+      validations:
+          required: true
+
+    - type: "checkboxes"
+      id: "module-system"
+      attributes:
+          label: "Which module system do you use?"
+          options:
+              - label: "CJS"
+              - label: "ESM"
+
+    - type: "dropdown"
+      id: "package-manager"
+      attributes:
+          label: "Used Package Manager"
+          description: "Select the used package manager"
+          options:
+              - "npm"
+              - "yarn"
+              - "pnpm"
+              - "other"
+      validations:
+          required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,31 @@
+name: "\U0001F680 New feature proposal"
+description: "Propose a new feature"
+labels: ["s: pending triage", "c: feature", "s: waiting for user interest"]
+body:
+    - type: "markdown"
+      attributes:
+          value: "Thanks for your interest in the project and taking the time to fill out this feature report!"
+    - type: "textarea"
+      id: "feature-description"
+      attributes:
+          label: "Clear and concise description of the problem"
+          description: "As a developer I want [goal / wish] so that [benefit]. If you intend to submit a PR for this issue, tell us in the description. Thanks!"
+      validations:
+          required: true
+    - type: "textarea"
+      id: "suggested-solution"
+      attributes:
+          label: "Suggested solution"
+          description: "In module [xy] we could provide following implementation..."
+      validations:
+          required: true
+    - type: "textarea"
+      id: "alternative"
+      attributes:
+          label: "Alternative"
+          description: "Clear and concise description of any alternative solutions or features you've considered."
+    - type: "textarea"
+      id: "additional-context"
+      attributes:
+          label: "Additional context"
+          description: "Any other context about the feature request here."

.github/ISSUE_TEMPLATE/freestyle.md

@@ -0,0 +1,5 @@
+---
+name: "Freestyle Report"
+about: "Create a report to help us improve"
+labels: "s: pending triage" # This will automatically assign the 'pending triage' label
+---