@amimpact/willy-utils 5.0.0 → 5.0.1

package/.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "snyk.advanced.autoSelectOrganization": true
+}

package/bitbucket-pipelines.yml

@@ -0,0 +1,13 @@
+image: node:24
+
+clone:
+  depth: full
+
+pipelines:
+  tags:
+    'v*': # Triggert ALLEEN wanneer een developer een tag pusht (bijv. v4.14.3)
+      - step:
+          name: Publish to npm
+          script:
+            - chmod +x ./scripts/publish-npm.sh
+            - ./scripts/publish-npm.sh

package/package.json

@@ -1,14 +1,11 @@
 {
     "name": "@amimpact/willy-utils",
-    "version": "5.0.0",
+    "version": "5.0.1",
     "description": "Javascript utils",
     "scripts": {
-        "publish:prerelease": "npm version prerelease --preid beta && npm publish --tag beta",
-        "publish:prepatch": "npm version prepatch --preid beta && npm publish --tag beta",
-        "publish:patch": "npm version patch && npm publish",
-        "publish:preminor": "npm version preminor --preid beta && npm publish --tag beta",
-        "publish:minor": "npm version minor && npm publish",
-        "postpublish": "git push origin --all; git push origin --tags"
+        "version:patch": "npm version patch",
+        "version:minor": "npm version minor",
+        "postversion": "git push origin HEAD && git push origin --tags"
     },
     "repository": {
         "type": "git",

package/scripts/publish-npm.sh

@@ -0,0 +1,71 @@
+#!/usr/bin/env bash
+
+set -e
+
+# Zorg dat de .npmrc ALTIJD wordt verwijderd bij afsluiten of crash
+cleanup() {
+    if [ -f .npmrc ]; then
+        rm .npmrc
+        echo "🧹 Tijdelijke .npmrc netjes opgeruimd."
+    fi
+}
+trap cleanup EXIT
+
+# 1. Veiligheidscheck: Bestaat de token?
+if [ -z "${NPM_TOKEN_PUBLISH}" ]; then
+    echo "ERROR: NPM_TOKEN_PUBLISH is not set. Cannot authenticate against the npm registry."
+    exit 1
+fi
+
+echo "Generating .npmrc with authentication for registry.npmjs.org..."
+echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN_PUBLISH}" > .npmrc
+
+# 2. Package gegevens ophalen
+PACKAGE_NAME="$(node -p "require('./package.json').name")"
+PACKAGE_VERSION="$(node -p "require('./package.json').version")"
+
+if [ -z "${PACKAGE_NAME}" ] || [ -z "${PACKAGE_VERSION}" ]; then
+    echo "ERROR: Could not read package name or version from package.json."
+    exit 1
+fi
+
+echo "Package: ${PACKAGE_NAME}"
+echo "Version: ${PACKAGE_VERSION}"
+
+# 3. Check of deze versie al op NPM staat
+EXISTING_VERSION="$(npm view "${PACKAGE_NAME}@${PACKAGE_VERSION}" version 2>/dev/null || true)"
+
+if [ -n "${EXISTING_VERSION}" ]; then
+    echo "Version ${PACKAGE_VERSION} of ${PACKAGE_NAME} is already published on npm. Skipping publish."
+    exit 0
+fi
+
+# 4. Veiligheidscheck: Is dit gestart door een Tag?
+if [ -z "${BITBUCKET_TAG}" ]; then
+    echo "ERROR: BITBUCKET_TAG is not set. This script must be run from a tag trigger."
+    exit 1
+fi
+
+echo "Current Git Tag: ${BITBUCKET_TAG}"
+
+# 5. DE MAGIE: Haal remote info op en check op welke branch deze tag leeft
+echo "Fetching remote branch information..."
+git fetch origin --quiet
+
+# We kijken of 'origin/master' of 'origin/main' voorkomt in de branches die deze tag bevatten
+IS_ON_MASTER="$(git branch -r --contains HEAD | grep -E 'origin/(master|main)' || true)"
+
+if [ -n "${IS_ON_MASTER}" ]; then
+    echo "🌍 Tag is part of the master/main branch. Publishing as 'latest'..."
+    npm publish
+    exit 0
+fi
+
+# 6. Als de tag niet op master staat, is het een oudere release branch
+# We pakken de Major.Minor van de versie (bijv. 4.14.3 -> 4.14) om de npm-tag te bepalen
+MAJOR_MINOR="$(echo "${PACKAGE_VERSION}" | cut -d. -f1,2)"
+NPM_TAG="release-${MAJOR_MINOR}"
+
+echo "📦 Tag is on a release branch. Publishing with tag '${NPM_TAG}'..."
+npm publish --tag "${NPM_TAG}"
+exit 0