Merge branch 'development' into nc-profile-merge-update

Author: NicoletaComan

.github/workflows/branch-deletion-pr-creation.yml

@@ -0,0 +1,110 @@
+name: Branch Deletion Phase One (PR Creation)
+permissions:
+  contents: write
+  pull-requests: write
+on:
+  schedule:
+    - cron: '00 22 1 * *'  # 10PM on 1st of every month
+  workflow_dispatch:
+    inputs:
+      min_age_days:
+        description: "Minimum age in days since merge"
+        required: true
+        default: 27
+        type: number
+
+jobs:
+  identify-branches:
+    if: github.repository_owner == 'mendix'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+          persist-credentials: true
+
+      - name: Setup jq
+        run: sudo apt-get install -y jq
+
+      - name: Create timestamp file
+        run: |
+          echo "Last scan for stale merged branches: $(TZ='Europe/Amsterdam' date +'%Y-%m-%d %H:%M:%S %Z (UTC%:z)')" > branch-cleanup-timestamp.txt
+
+      - name: Fetch all branches
+        run: |
+          git fetch origin '+refs/heads/*:refs/remotes/origin/*' --prune
+
+      - name: Process branches
+        id: branch-data
+        run: |
+          set -e
+          ALL_BRANCHES=$(git branch -r | grep -v "origin/HEAD" | sed 's/origin\///')
+          MIN_AGE_DAYS=${{ github.event.inputs.min_age_days || 27 }}
+
+          PROTECTED_BRANCHES=()
+          MERGED_BRANCHES_TO_PROCESS=()
+          BRANCHES_TO_DELETE=()
+          BRANCHES_TOO_RECENT=()
+          UNMERGED_BRANCHES=()
+
+          CURRENT_DATE=$(date +%Y%m%d)
+          echo "CURRENT_DATE=$CURRENT_DATE" >> $GITHUB_ENV
+
+          for BRANCH in $ALL_BRANCHES; do
+            branch_lower=$(echo "$BRANCH" | tr '[:upper:]' '[:lower:]')
+            if [[ $branch_lower =~ (backup|development|main|master|production) ]]; then
+              PROTECTED_BRANCHES+=("$BRANCH (protected)")
+            elif git branch -r --merged origin/development | grep -q "origin/$BRANCH"; then
+              MERGED_BRANCHES_TO_PROCESS+=("$BRANCH")
+            else
+              UNMERGED_BRANCHES+=("$BRANCH (not merged)")
+            fi
+          done
+
+          for BRANCH in "${MERGED_BRANCHES_TO_PROCESS[@]}"; do
+            MERGE_HASH=$(git log --grep="Merge branch.*$BRANCH" origin/development -n 1 --pretty=format:"%H" || true)
+            [ -z "$MERGE_HASH" ] && MERGE_HASH=$(git log -n 1 origin/$BRANCH --pretty=format:"%H")
+            
+            MERGE_DATE=$(git show -s --format=%ct $MERGE_HASH)
+            DAYS_AGO=$(( ($(date +%s) - MERGE_DATE) / 86400 ))
+            
+            if [[ $DAYS_AGO -ge $MIN_AGE_DAYS ]]; then
+              BRANCHES_TO_DELETE+=("$BRANCH")
+            else
+              BRANCHES_TOO_RECENT+=("$BRANCH (too recent: ${DAYS_AGO}d)")
+            fi
+          done
+
+           ALL_NON_DELETED=(
+            "${PROTECTED_BRANCHES[@]}" 
+            "${BRANCHES_TOO_RECENT[@]}"
+            "${UNMERGED_BRANCHES[@]}"
+          )
+
+          echo "HAS_BRANCHES=$([ ${#BRANCHES_TO_DELETE[@]} -gt 0 ] && echo true || echo false)" >> $GITHUB_ENV
+          echo "BRANCHES_TO_DELETE=$(printf -- '- %s\n' "${BRANCHES_TO_DELETE[@]}" | jq -Rs .)" >> $GITHUB_ENV
+          echo "ALL_NON_DELETED=$(printf -- '- %s\n' "${ALL_NON_DELETED[@]}" | jq -Rs .)" >> $GITHUB_ENV
+
+      - name: Create Deletion PR
+        if: env.HAS_BRANCHES == 'true'
+        uses: peter-evans/create-pull-request@v6
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          title: "[Auto] Branch Deletion Candidates - ${{ env.CURRENT_DATE }}"
+          body: |
+            ### Branches for Deletion
+            ${{ fromJSON(env.BRANCHES_TO_DELETE) }}
+
+            ### Protected/Recent Branches
+            ${{ fromJSON(env.ALL_NON_DELETED) }}
+          base: development
+          labels: Internal WIP
+          assignees: MarkvanMents,OlufunkeMoronfolu
+          reviewers: MarkvanMents,OlufunkeMoronfolu
+          commit-message: "Add branch cleanup candidates for ${{ env.CURRENT_DATE }}"
+          add-paths: |
+            branch-cleanup-timestamp.tx
+          author: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"
+          committer: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"

.github/workflows/branch-deletion-pr-processing.yml

@@ -0,0 +1,64 @@
+name: Branch Deletion Phase Two (PR Processing)
+on:
+  pull_request:
+    types: [closed]
+    branches: [development]
+    paths:
+      - 'branch-cleanup-timestamp.txt'
+
+permissions:
+  contents: write
+
+jobs:
+  process-approved-deletion:
+    if: |
+      github.event.pull_request.merged == true &&
+      startsWith(github.event.pull_request.title, '[Auto] Branch Deletion Candidates') &&
+      contains(github.event.pull_request.labels.*.name, 'Internal WIP')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+          persist-credentials: true
+
+      - name: Extract branches
+        id: extract-branches
+        env:
+          PR_BODY: ${{ github.event.pull_request.body }}
+        run: |
+          BRANCHES=$(echo "$PR_BODY" | awk '
+            /### Branches for Deletion/ {flag=1; next}
+            /### Protected\/Recent Branches/ {flag=0}
+            flag && /^-/ {gsub(/^-[ \t]*/, ""); print}
+          ')
+          
+          CLEAN_BRANCHES=$(echo "$BRANCHES" | tr -d '\r' | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
+          echo "branches=$(jq -nc '$ARGS.positional' --args $CLEAN_BRANCHES)" >> $GITHUB_OUTPUT
+          echo "Extracted branches: $BRANCHES"
+
+      - name: Delete branches
+        env:
+          BRANCHES: ${{ steps.extract-branches.outputs.branches }}
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+          echo "$BRANCHES" | jq -r '.[]' | while read -r branch; do
+            branch_lower=$(echo "$branch" | tr '[:upper:]' '[:lower:]')
+            
+            if [[ $branch_lower =~ ^(backup|development|main|master|production)(-[0-9]+)?$ ]]; then
+              echo "Skipping protected branch: $branch"
+              continue
+            fi
+
+            if git ls-remote --exit-code --heads origin "$branch" >/dev/null; then
+              echo "Deleting $branch"
+              git push origin --delete "$branch"
+              sleep 1
+            else
+              echo "Branch $branch does not exist"
+            fi
+          done

.github/workflows/lint-action.yml

@@ -53,7 +53,8 @@ jobs:
           body: |
             ${{ env.VER }}
           branch: lint-docs
-          committer: MarkvanMents <Mark.van.Ments@mendix.com>
+          author: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"
+          committer: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"
           assignees: MarkvanMents,OlufunkeMoronfolu
           reviewers: MarkvanMents,OlufunkeMoronfolu
           labels: Internal WIP

.github/workflows/remunusedattachments.yml

@@ -36,7 +36,8 @@ jobs:
             Pull Request to delete attachments that are no longer used.
             Check the htmltest output from the CI/CD pipeline to ensure that nothing has been removed accidentally.
           branch: rem-unused-attachments
-          committer: MarkvanMents <Mark.van.Ments@mendix.com>
+          author: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"
+          committer: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"
           assignees: MarkvanMents,OlufunkeMoronfolu
           reviewers: MarkvanMents,OlufunkeMoronfolu
           labels: Internal WIP

assets/scss/_styles_project.scss

@@ -257,7 +257,7 @@ div.date-format{
 
 // DB – Add borders around images
 main img {
-    border-color: #d7d7d7;
+    border-color: $gray-400;
     border-width: 1px;
     border-style: solid;
 }

branch-cleanup-timestamp.txt

@@ -0,0 +1 @@
+Last scan for stale merged branches: 2025-12-01 23:24:23 CET (UTC+01:00)

content/en/docs/apidocs-mxsdk/apidocs/deployment/build-api.md

@@ -296,9 +296,9 @@ An object with the following key-value pairs:
 
 {{% alert color="warning" %}}
 
-- For apps using SVN for version control, this call will build the specified revision even if that revision is not on the specified branch.
+* For apps using SVN for version control, this call will build the specified revision even if that revision is not on the specified branch.
 
-- For apps using Git for version control, using a short commit hash can cause timeouts with large repositories. Mendix recommends using the full commit hash
+* For apps using Git for version control, using a short commit hash can cause timeouts with large repositories. Mendix recommends using the full commit hash
 {{% /alert %}}
 
 ##### Example

content/en/docs/apidocs-mxsdk/apidocs/governance/project-category-api.md

@@ -0,0 +1,37 @@
+---
+title: "Project Category API"
+url: /apidocs-mxsdk/apidocs/project-category-api/
+type: swagger
+description: "The Project Category API manages your project categories."
+weight: 100
+restapi: true
+---
+
+## Introduction
+
+The Mendix Project Category API allows you to create, edit or delete your project categories.
+
+## Authentication {#authentication}
+
+Authentication for the Project Category API uses a personal access token (PAT).
+
+### Generating a PAT {#generate}
+
+For details on how to generate a PAT, refer to the [Personal Access Tokens](/mendix-profile/user-settings/#pat) section of *User Settings*.
+
+Select the appropriate scopes, depending on the endpoints that need to be invoked. Refer to the [API Reference](#api-reference) for more information on which scopes to use in which endpoints.
+
+Store the generated value somewhere safe so you can use it to authorize your API calls.
+
+### Using the PAT
+
+Each request must contain an `Authorization` header with the value `MxToken {GENERATED_PAT}`. For example:
+
+```http
+GET /companies/{:companyId}/categories HTTP/1.1
+Authorization: MxToken 7LJE…vk
+```
+
+## API Reference{#api-reference}
+
+{{< swaggerui-disable-try-it-out src="/openapi-spec/categories-v1.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api.md

@@ -0,0 +1,26 @@
+---
+title: "Private Mendix Platform Pipeline API"
+url: /apidocs-mxsdk/apidocs/private-platform-pipeline-api/
+type: swagger
+description: "This API allows you to manage pipelines in Private Mendix Platform."
+restapi: true
+weight: 60
+linktitle: "Pipeline API"
+---
+
+{{% alert color="info" %}}
+This document is about [Private Mendix Platform](/private-mendix-platform/) API. This API is only available on instances of Private Mendix Platform. For [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) API, see [Mendix on Kubernetes Build API](/apidocs-mxsdk/apidocs/private-cloud-build-api/) and [Mendix on Kubernetes Deploy API](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/).
+{{% /alert %}}
+
+## Introduction
+
+The Private Mendix Platform Project API allows you to manage pipelines in Private Mendix Platform. You can use the API to do the following:
+
+* Get pipeline running information.
+* Set the current step status of the pipeline.
+* Create a pipeline for build or deployment.
+* Approve or reject a manual step of a waiting pipeline.
+
+## API Reference
+
+{{< swaggerui src="/openapi-spec/openapi-pipeline.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/_index.md

@@ -20,6 +20,6 @@ For information on new releases of the Extensibility API see:
 
 ## Introduction
 
-Extensions are self-contained modules which users can add to Studio Pro. This means that with extensibility you can add new features and functionality to Studio Pro. The Extensibility API is an API that allows developers to interact with a curated list of internal systems of Studio Pro. This documentation provides guides and reference documentation for the Extensibility API.
+Extensions are self-contained modules that enhance Studio Pro by adding new features and functionality. The Extensibility API allows you to interact with a curated set of internal systems, extending Studio Pro’s capabilities with functionality you can define yourself.
 
-The API is provided in two flavors, depending which language you are developing in. C# and web based (via Typescript):
+The API is provided in two versions, depending on the language you are developing in: