chore: manually resolved conflicting changes from origin

Author: amanstep

.eslintrc.js

@@ -19,8 +19,9 @@ See [Conventional Commits](https://www.conventionalcommits.org/) for more exampl
 
 1. If your goal is to create squashed commits that will be used for automated releases, you'll want to configure your GitHub repository to [use the squash & merge strategy](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests) and tick the option "Default to PR title for squash merge commits".
 2. [Add the action](https://docs.github.com/en/actions/quickstart) with the following configuration:
+
 ```yml
-name: "Lint PR"
+name: 'Lint PR'
 
 on:
   pull_request_target:
@@ -36,7 +37,7 @@ jobs:
     permissions:
       pull-requests: read
     steps:
-      - uses: step-security/action-semantic-pull-request@v5
+      - uses: step-security/action-semantic-pull-request@v6
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 ```
@@ -123,7 +124,7 @@ This will prevent the PR title from being validated, and pull request checks wil
 **Attention**: If you want to use the this feature, you need to grant the `pull-requests: write` permission to the GitHub Action. This is because the action will update the status of the PR to remain in a pending state while `[WIP]` is present in the PR title.
 
 ```yml
-name: "Lint PR"
+name: 'Lint PR'
 
 permissions:
   pull-requests: write
@@ -135,7 +136,7 @@ jobs:
     permissions:
       pull-requests: read
     steps:
-      - uses: step-security/action-semantic-pull-request@v5
+      - uses: step-security/action-semantic-pull-request@v6
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
@@ -144,7 +145,7 @@ jobs:
 
 ### Legacy configuration for validating single commits
 
-When using "Squash and merge" on a PR with only one commit, GitHub will suggest using that commit message instead of the PR title for the merge commit. As it's easy to commit this by mistake this action supports two configuration options to provide additional validation for this case. 
+When using "Squash and merge" on a PR with only one commit, GitHub will suggest using that commit message instead of the PR title for the merge commit. As it's easy to commit this by mistake this action supports two configuration options to provide additional validation for this case.
 
 ```yml
           # If the PR only contains a single commit, the action will validate that
@@ -174,8 +175,8 @@ There are two events that can be used as triggers for this action, each with dif
 <details>
 <summary>Example</summary>
 
-```yml
-name: "Lint PR"
+````yml
+name: 'Lint PR'
 
 on:
   pull_request_target:
@@ -193,7 +194,7 @@ jobs:
     permissions:
       pull-requests: read
     steps:
-      - uses: step-security/action-semantic-pull-request@v5
+      - uses: step-security/action-semantic-pull-request@v6
         id: lint_pr_title
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -206,21 +207,21 @@ jobs:
           header: pr-title-lint-error
           message: |
             Hey there and thank you for opening this pull request! 👋🏼
-            
+
             We require pull request titles to follow the [Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/) and it looks like your proposed title needs to be adjusted.
 
             Details:
-            
+
             ```
             ${{ steps.lint_pr_title.outputs.error_message }}
             ```
 
       # Delete a previous comment when the issue has been resolved
       - if: ${{ steps.lint_pr_title.outputs.error_message == null }}
         uses: marocchino/sticky-pull-request-comment@v2
-        with:   
+        with:
           header: pr-title-lint-error
           delete: true
-```
+````
 
 </details>

README.md

@@ -0,0 +1,11 @@
+import {getPresets} from 'eslint-config-molindo';
+import globals from 'globals';
+
+export default [
+  ...(await getPresets('javascript', 'vitest')),
+  {
+    languageOptions: {
+      globals: globals.node
+    }
+  }
+];

eslint.config.mjs

@@ -4,9 +4,9 @@
   "description": "Ensure your PR title matches the Conventional Commits spec.",
   "main": "dist/index.js",
   "scripts": {
-    "lint": "eslint src",
-    "test": "jest src",
-    "build": "rm -rf dist && ncc build"
+    "lint": "eslint src && prettier --check src",
+    "test": "vitest src",
+    "build": "rm -rf dist && rollup -c"
   },
   "repository": {
     "type": "git",
@@ -37,5 +37,6 @@
   },
   "engines": {
     "node": "^20.0.0"
-  }
+  },
+  "prettier": "eslint-config-molindo/.prettierrc.json"
 }

package.json

@@ -0,0 +1,18 @@
+// See: https://rollupjs.org/introduction/
+
+import commonjs from '@rollup/plugin-commonjs';
+import json from '@rollup/plugin-json';
+import {nodeResolve} from '@rollup/plugin-node-resolve';
+
+const config = {
+  input: 'src/index.js',
+  output: {
+    esModule: true,
+    file: 'dist/index.js',
+    format: 'es',
+    sourcemap: true
+  },
+  plugins: [commonjs(), nodeResolve({preferBuiltins: true}), json()]
+};
+
+export default config;

rollup.config.js

@@ -1,10 +1,9 @@
-const core = require('@actions/core');
-const github = require('@actions/github');
-const axios = require('axios');
-const parseConfig = require('./parseConfig');
-const validatePrTitle = require('./validatePrTitle');
+import core from '@actions/core';
+import github from '@actions/github';
+import parseConfig from './parseConfig.js';
+import validatePrTitle from './validatePrTitle.js';
 
-module.exports = async function run() {
+export default async function run() {
   try {
     await validateSubscription();
     const {
@@ -118,6 +117,7 @@ module.exports = async function run() {
                 headerPattern,
                 headerPatternCorrespondence
               });
+              // eslint-disable-next-line unicorn/prefer-optional-catch-binding, no-unused-vars -- Legacy syntax for compatibility
             } catch (error) {
               throw new Error(
                 `Pull request has only one commit and it's not semantic; this may lead to a non-semantic commit in the base branch (see https://github.com/community/community/discussions/16271 ). Amend the commit message to match the pull request title, or add another commit.`
@@ -158,8 +158,8 @@ module.exports = async function run() {
         description: isWip
           ? 'This PR is marked with "[WIP]".'
           : validationError
-          ? 'PR title validation failed'
-          : 'Ready for review & merge.',
+            ? 'PR title validation failed'
+            : 'Ready for review & merge.',
         context: 'action-semantic-pull-request'
       });
     }