NP-790: Fix bundle not working in Github action

.github/workflows/test.yml

@@ -17,5 +17,9 @@ jobs:
       - run: npm ci
       - run: npm run lint
       - run: npm run check
-      - run: npm test
+      # Build before test: the bundle-smoke test in `tests/` loads the
+      # compiled `lib/main.js`, and running `npm run build` first also
+      # surfaces missing-file / bundler-config regressions before the
+      # (slower) full Vitest suite runs.
       - run: npm run build
+      - run: npm test

README.md

@@ -39,7 +39,7 @@ jobs:
       - uses: actions/checkout@v6
       - name: Bump version and push tag
         id: tag_version
-        uses: mathieudutour/github-tag-action@v6.1
+        uses: StackAdapt/github-tag-action@v7.0.0
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
       - name: Create a GitHub release
@@ -61,7 +61,7 @@ jobs:
 
 #### Filter branches
 
-- **release_branches** _(optional)_ - Comma separated list of branches (JavaScript regular expression accepted) that will generate the release tags. Other branches and pull-requests generate versions postfixed with the commit hash and do not generate any repository tag. Examples: `master` or `.*` or `release.*,hotfix.*,master`... (default: `master,main`).
+- **release_branches** _(optional)_ - Comma separated list of branches (JavaScript regular expression accepted) that will generate release tags. On any other branch (and on pull requests) the action logs "Skipping the tag creation" and exits without tagging the repository — no commit-hash-postfixed versions are computed or emitted. Examples: `master` or `.*` or `release.*,hotfix.*,master`... (default: `master,main`).
 - **pre_release_branches** _(optional)_ - Comma separated list of branches (JavaScript regular expression accepted) that will generate the pre-release tags.
 
 #### Customize the tag
@@ -91,8 +91,8 @@ jobs:
 
 - **new_tag** - The value of the newly calculated tag. Note that if there hasn't been any new commit, this will be `undefined`.
 - **new_version** - The value of the newly created tag without the prefix. Note that if there hasn't been any new commit, this will be `undefined`.
-- **previous_tag** - The value of the previous tag (or `v0.0.0` if none). Note that if `custom_tag` is set, this will be `undefined`.
-- **previous_version** - The value of the previous tag (or `0.0.0` if none) without the prefix. Note that if `custom_tag` is set, this will be `undefined`.
+- **previous_tag** - The value of the previous tag. When no tag exists yet, defaults to a synthetic `{tag_prefix}0.0.0` (e.g. `v0.0.0` with the default prefix). Note that if `custom_tag` is set, this will be `undefined`.
+- **previous_version** - The value of the previous tag without the prefix (e.g. `0.0.0` when no tag exists yet). Note that if `custom_tag` is set, this will be `undefined`.
 - **release_type** - The computed release type (`major`, `minor`, `patch` or `custom` - can be prefixed with `pre`).
 - **changelog** - The [conventional changelog](https://github.com/conventional-changelog/conventional-changelog) since the previous tag.
 

action.yml

@@ -7,7 +7,9 @@ outputs:
   new_version:
     description: 'Generated tag without the prefix'
   previous_tag:
-    description: 'Previous tag (or `0.0.0`)'
+    description: 'Previous tag. When no tag exists yet, defaults to a synthetic `{tag_prefix}0.0.0` (e.g. `v0.0.0`).'
+  previous_version:
+    description: 'Previous tag without the `tag_prefix` (e.g. `0.0.0` when no tag exists yet).'
   release_type:
     description: 'The computed release type (`major`, `minor`, `patch` or `custom` - can be prefixed with `pre`)'
   changelog:
@@ -38,11 +40,11 @@ inputs:
     description: 'Comma separated list of release rules. Format: `<keyword>:<release_type>`. Example: `hotfix:patch,pre-feat:preminor`.'
     required: false
   release_branches:
-    description: 'Comma separated list of branches (bash reg exp accepted) that will generate the release tags. Other branches and pull-requests generate versions postfixed with the commit hash and do not generate any tag. Examples: `master` or `.*` or `release.*,hotfix.*,master`...'
+    description: 'Comma separated list of branches (JavaScript regular expression accepted, matched via `String.prototype.match`) that will generate release tags. On any other branch — and on pull requests — the action logs "Skipping the tag creation" and exits without pushing a tag. Examples: `master` or `.*` or `release.*,hotfix.*,master`...'
     required: false
     default: 'master,main'
   pre_release_branches:
-    description: 'Comma separated list of branches (bash reg exp accepted) that will generate pre-release tags.'
+    description: 'Comma separated list of branches (JavaScript regular expression accepted, matched via `String.prototype.match`) that will generate pre-release tags.'
     required: false
   commit_sha:
     description: 'The commit SHA value to add the tag. If specified, it uses this value instead GITHUB_SHA. It could be useful when a previous step merged a branch into github.ref.'