Studio Frontend Build: scope push trigger to version branches

.github/CODEOWNERS

@@ -0,0 +1 @@
+.github/workflows/ @bluvulture @berfinyuksel

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,12 @@
 blank_issues_enabled: false
 contact_links:
-    - name: We are hiring!
-      url: https://pimcore.com/en/careers?utm_source=github&utm_medium=issue-template-data-hub&utm_campaign=careers
-      about: Enjoy working with Pimcore? Join us on our mission!
-    - name: Community Support
-      url: https://github.com/pimcore/pimcore/discussions
-      about: Please ask and answer questions here.
+  - name: Platform Repository (Public Issues)
+    url: https://github.com/pimcore/platform-version/issues
+    about: Public place to report reproducible issues affecting the Pimcore platform. You may receive support from the community or other users. Please search for existing issues before creating a new one.
+  - name: Support Portal (Private Issues)
+    url: https://get.support.pimcore.com/
+    about: Private channel to report bugs. Issues and issue details are only shared between you and Pimcore and are not visible to other users. This does not include prioritization or additional support.
+  - name: Community Support (Discussions)
+    url: https://github.com/pimcore/pimcore/discussions
+    about: For questions, ideas, and general discussions. This is the preferred place for community-driven support and knowledge exchange.
+

.github/ci/files/config/bundles.php

@@ -1,6 +1,7 @@
 <?php
 
 return [
-    \Pimcore\Bundle\AdminBundle\PimcoreAdminBundle::class => ['all' => true],
-    \Pimcore\Bundle\DataHubBundle\PimcoreDataHubBundle::class => ['all' => true]
+    Pimcore\Bundle\DataHubBundle\PimcoreDataHubBundle::class => ['all' => true],
+    Pimcore\Bundle\StudioBackendBundle\PimcoreStudioBackendBundle::class => ['all' => true],
+    Pimcore\Bundle\StudioUiBundle\PimcoreStudioUiBundle::class => ['all' => true],
 ];

.github/ci/files/config/packages/security.yaml

@@ -8,24 +8,20 @@ security:
             pattern: ^/(_(profiler|wdt)|css|images|js)/
             security: false
 
+        pimcore_studio: '%pimcore_studio_backend.firewall_settings%'
+
         # Pimcore WebDAV HTTP basic // DO NOT CHANGE!
         pimcore_webdav:
             pattern: ^/asset/webdav
             provider: pimcore_admin
             http_basic: ~
 
-        pimcore_admin: '%pimcore_admin_bundle.firewall_settings%'
-
     access_control:
         # Pimcore admin ACl  // DO NOT CHANGE!
-        - { path: ^/admin/settings/display-custom-logo, roles: PUBLIC_ACCESS }
-        - { path: ^/admin/login/2fa-verify, roles: IS_AUTHENTICATED_2FA_IN_PROGRESS }
-        - { path: ^/admin/login/2fa-setup, roles: ROLE_PIMCORE_USER }
-        - { path: ^/admin/login/2fa, roles: IS_AUTHENTICATED_2FA_IN_PROGRESS }
-        - { path: ^/admin/login$, roles: PUBLIC_ACCESS }
-        - { path: ^/admin/login/(login|lostpassword|deeplink|csrf-token)$, roles: PUBLIC_ACCESS }
-        - { path: ^/admin, roles: ROLE_PIMCORE_USER }
+        - { path: ^/pimcore-studio/api/(docs|docs/json|translations|user/reset-password)$, roles: PUBLIC_ACCESS }
+        - { path: ^/pimcore-studio/api, roles: ROLE_PIMCORE_USER }
+        - { path: ^/asset/webdav, roles: ROLE_PIMCORE_USER }
 
     role_hierarchy:
         # Pimcore admin  // DO NOT CHANGE!
-        ROLE_PIMCORE_ADMIN: [ROLE_PIMCORE_USER]
+        ROLE_PIMCORE_ADMIN: [ROLE_PIMCORE_USER]

.github/ci/files/config/packages/test/config.yaml

@@ -23,7 +23,6 @@ doctrine:
                 user: ~
                 password: ~
                 mapping_types:
-                    enum: string
                     bit: boolean
 
 pimcore:

.github/workflows/copilot-setup-steps.yml

@@ -0,0 +1,46 @@
+name: "Copilot Setup Steps"
+
+# Automatically run the setup steps when they are changed to allow for easy validation, and
+# allow manual testing through the repository's "Actions" tab
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+  pull_request:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+
+jobs:
+  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
+  # The steps MUST be defined inline here: the Copilot coding agent only reads `steps`
+  # (plus permissions/runs-on/services/snapshot/timeout-minutes) from this job, so a
+  # reusable-workflow `uses:` call would be ignored by Copilot.
+  copilot-setup-steps:
+    runs-on: ubuntu-latest
+
+    permissions:
+      contents: read
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: "Install PHP"
+        uses: "shivammathur/setup-php@v2"
+        with:
+          php-version: "8.4"
+
+      - name: "Add authentication for private pimcore packages"
+        run: |
+          composer config repositories.private-packagist '{"type": "composer", "url": "https://repo.pimcore.com/github-actions/", "canonical": true}'
+          composer config --global --auth http-basic.repo.pimcore.com github-actions ${{ secrets.COMPOSER_PIMCORE_REPO_PACKAGIST_TOKEN }}
+
+      - name: "Install dependencies with Composer"
+        uses: "ramsey/composer-install@v3"
+        with:
+          composer-options: "--no-scripts --ignore-platform-reqs"
+
+      - name: Restore composer.json
+        if: ${{ always() }}
+        run: git restore composer.json

.github/workflows/pr-policy.yml

@@ -0,0 +1,42 @@
+name: PR Policy
+
+# Enforces PR requirements before merge. Make the "Milestone assigned" check required
+# (repo ruleset / branch protection) so it actually blocks merging.
+
+on:
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - synchronize
+      - ready_for_review
+      - milestoned
+      - demilestoned
+
+permissions:
+  contents: read
+
+jobs:
+  milestone:
+    name: Milestone assigned
+    if: github.event.pull_request.draft == false
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check milestone
+        env:
+          MILESTONE: ${{ github.event.pull_request.milestone.title }}
+          AUTHOR: ${{ github.event.pull_request.user.login }}
+        run: |
+          # Automated sync PRs (repo-file-sync-action) never carry a milestone.
+          if [ "$AUTHOR" = "pimcore-deployments" ]; then
+            echo "Skipping milestone check for automated PR by $AUTHOR"
+            exit 0
+          fi
+
+          if [ -z "$MILESTONE" ]; then
+            echo "::error::A milestone must be assigned before this pull request can be merged."
+            exit 1
+          fi
+
+          echo "Milestone assigned: $MILESTONE"

.github/workflows/studio-frontend-build.yaml

@@ -0,0 +1,28 @@
+name: "Studio Frontend Build"
+
+on:
+  push:
+    branches:
+      - "[0-9]+.x"
+      - "[0-9]+.[0-9]+"
+    paths:
+      - "assets/studio/**"
+      - "src/Resources/public/studio/build/**"
+  pull_request:
+    paths:
+      - "assets/studio/**"
+      - "src/Resources/public/studio/build/**"
+  workflow_dispatch:
+
+concurrency:
+  group: studio-frontend-build-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
+
+permissions:
+  contents: write
+
+jobs:
+  studio-frontend-build:
+    uses: pimcore/workflows-collection-public/.github/workflows/reusable-studio-frontend-build.yaml@main
+    with:
+      build-output-path: './src/Resources/public/studio/'

CONTRIBUTING.md

@@ -17,9 +17,9 @@ We gladly accept community pull requests.
 There are a few necessary steps before we can accept a pull request:
 
 * [Fork us!](https://help.github.com/articles/fork-a-repo/)
-* Select the right branch. main(e.g. 1.x) for features and improvements or latest maintenance branch for bug fixes (e.g. 1.0)
-* Code! Follow the coding standards defined [here](https://github.com/pimcore/data-hub/blob/1.x/.php-cs-fixer.dist.php).
-* [Send a pull request](https://help.github.com/articles/using-pull-requests/) from your fork’s branch to our `master` branch.
+* Select the right branch. default branch (e.g. 2026.x) for features and improvements or latest maintenance branch for bug fixes (e.g. 2026.2)
+* Code! Follow the coding standards defined [here](./.php-cs-fixer.dist.php).
+* [Send a pull request](https://help.github.com/articles/using-pull-requests/) from your fork’s branch to the branch you selected above.
 * [Sign the CLA](https://cla-assistant.io/pimcore/data-hub) - see also below.
 
 

README.md

@@ -26,16 +26,20 @@ A short introduction video of an output channel based on the GraphQL query langu
 ## Documentation Overview
 - [Installation](./doc/01_Installation_and_Upgrade/README.md)
 - [Basic principle](./doc/02_Basic_Principle.md) for configuring an endpoint
+- [Customization](./doc/05_Customization.md) for the Studio API events; permissions for the configuration panel are covered in
+  [Installation](./doc/01_Installation_and_Upgrade/README.md#user-permissions)
 - [GraphQL](./doc/10_GraphQL/README.md) [*default and recommended endpoint*]
 - [Configuration & Deployment](./doc/20_Deployment.md)
 - [Testing](./doc/30_Testing.md)
 
 ## Further Information
 On Pimcore Datahub adapters:
-- [Datahub Simple Rest API](https://pimcore.com/docs/platform/Datahub_Simple_Rest/)
-- [Datahub File Export](https://pimcore.com/docs/platform/Datahub_File_Export/)
-- [Datahub Productsup](https://pimcore.com/docs/platform/Datahub_Productsup/)
+- [Data Importer](https://github.com/pimcore/data-importer/blob/2026.x/doc/01_Installation/README.md)
+- [Datahub Simple REST API](https://github.com/pimcore/data-hub-simple-rest/blob/2026.x/doc/01_Installation/README.md)
+- [Datahub File Export](https://github.com/pimcore/data-hub-file-export/blob/2026.x/doc/01_Installation/README.md)
+- [Datahub Productsup](https://github.com/pimcore/data-hub-productsup/blob/2026.x/doc/01_Installation/README.md)
+- [Datahub Webhooks](https://github.com/pimcore/data-hub-webhooks/blob/2026.x/doc/01_Installation/README.md)
 
 ## Contributions
 As Pimcore Datahub is a community project, any contributions highly appreciated.
-For details see our [Contributing guide](https://github.com/pimcore/data-hub/blob/master/CONTRIBUTING.md).
+For details see our [Contributing guide](./CONTRIBUTING.md).

SECURITY.md

@@ -1,22 +1,6 @@
 # Security Policy
 
-## Reporting a Vulnerability
+Please do not report security vulnerabilities here.
 
-If you think that you have found a security issue,
-don’t use the bug tracker and don’t publish it publicly.
-Instead, all security issues must be reported via a private vulnerability report.
-
-Please follow the [instructions](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability) to submit a private report.
-
-
-## Resolving Process
-Every submitted security issue is handled with top priority by following these steps:
-
-1. Confirm the vulnerability
-2. Determine the severity
-3. Contact reporter
-4. Work on a patch
-5. Get a CVE identification number (may be done by the reporter or a security service provider)
-6. Patch reviewing
-7. Tagging a new release for supported versions
-8. Publish security announcement
+Use our central security reporting process:
+[Platform Version Vulnerabilities](https://github.com/pimcore/platform-version/security/advisories)