Merge with main, Update deps, remove parcel

.eslintignore

@@ -4,3 +4,6 @@ packages/volto
 packages/volto-guillotina
 !.*
 dist
+packages/registry/lib
+packages/registry/docs
+apps/rr7/.react-router

.eslintrc.cjs

@@ -56,6 +56,7 @@ const config = {
       ],
       rules: {
         '@typescript-eslint/no-explicit-any': 'off',
+        '@typescript-eslint/ban-ts-comment': 0,
       },
     },
     {

.github/ISSUE_TEMPLATE/bug_report.md → .github/ISSUE_TEMPLATE/1_bug_report.md

@@ -1,8 +1,8 @@
 ---
-name: Bug report
-about: Create a report to help us improve Volto
+name: '🐞 Bug report'
+about: 'Create a report to help us improve Volto'
 title: ''
-labels: ['01 type: bug', 'needs: triage']
+labels: ['01 type: bug', '30 needs: triage']
 assignees: ''
 ---
 
@@ -13,23 +13,23 @@ A clear and concise description of what the bug is.
 Steps to reproduce the behavior:
 
 1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
+2. Click on '...'
+3. Scroll down to '...'
 4. See error
 
 **Expected behavior**
 A clear and concise description of what you expected to happen.
 
 **Screenshots**
-If applicable, add screenshots to help explain your problem.
+If applicable, add screenshots or videos to help explain your problem.
 
 **Software (please complete the following information):**
 
 - OS: [e.g. iOS]
-- Browser [e.g. chrome, safari]
-- Volto Version [e.g. 8.5.0]
-- Plone Version [e.g. 5.2.2]
-- Plone REST API Version [e.g. 7.0.1]
+- Browser [e.g. firefox, chrome, safari]
+- Volto Version [e.g. 18.4.0]
+- Plone Version [e.g. 6.1.0]
+- Plone REST API Version [e.g. 9.1.0]
 
 **Additional context**
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md → .github/ISSUE_TEMPLATE/2_feature_request.md

@@ -1,6 +1,6 @@
 ---
-name: Feature request
-about: Suggest an idea for Volto
+name: '🦄 Feature request'
+about: 'Suggest an idea for Volto'
 title: ''
 labels: '04 type: enhancement'
 assignees: ''

.github/ISSUE_TEMPLATE/PLIP.md → .github/ISSUE_TEMPLATE/3_PLIP.md

@@ -1,17 +1,23 @@
 ---
-name: "\U0001F680 PLIP"
-about: Plone Improvement Proposal
+name: '🚀 PLIP'
+about: 'A Plone Improvement Proposal (PLIP) is a change to a Plone package that would affect everyone who uses that package.'
 title: ''
-labels: ''
+labels: '03 type: feature (plip)'
+type: 'PLIP'
 assignees: ''
-
+projects: 'plone/47'
 ---
 
+<!-- Keep this admonition when you submit your PLIP -->
+
+> [!IMPORTANT]
+> If you are not a member of the Volto Team or Developers Team in the Plone GitHub organization, then do not work on or comment on this issue.
+
 ## PLIP (Plone Improvement Proposal)
 
 <!--
 
-Read http://5.docs.plone.org/develop/coredev/docs/plips.html first!
+Read https://6.docs.plone.org/contributing/core/plips.html first!
 
 Set "03 type: feature: plip" as label.
 

.github/ISSUE_TEMPLATE/4_PLIP_task.md

@@ -0,0 +1,26 @@
+---
+name: "📋 PLIP task"
+about: 'Plone Improvement Proposal (PLIP) tasks are sub-issues of the umbrella PLIP.'
+title: ''
+labels: '06 type: plip task'
+type: 'Feature'
+assignees: ''
+projects: 'plone/47'
+---
+
+<!-- Keep this admonition when you submit your PLIP task -->
+
+> [!IMPORTANT]
+> If you are not a member of the Volto Team or Developers Team in the Plone GitHub organization, then do not work on or comment on this issue.
+
+**Describe the PLIP task**
+
+A clear and concise description of what you want to happen, even if it is already in the PLIP. A conversation about this PLIP task should continue and extend from the PLIP.
+
+**Link to the parent PLIP**
+
+
+
+**Additional context**
+
+Add any other context or screenshots about the PLIP task here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Get support
+    url: https://community.plone.org/
+    about: Get support for Plone in the Community Forum.
+  - name: Chat
+    url: https://discord.gg/zFY3EBbjaj
+    about: Chat on Discord.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+> [!CAUTION]
+The Volto Team has suspended its review of new pull requests from first-time contributors until the [release of Plone 7](https://plone.org/download/release-schedule), which is preliminarily scheduled for the second quarter of 2026.
+> [Read details](https://6.docs.plone.org/volto/contributing/index.html).
+
+-----
+
+- [ ] I signed and returned the [Plone Contributor Agreement](https://plone.org/foundation/contributors-agreement), and received and accepted an invitation to join a team in the Plone GitHub organization.
+- [ ] I verified there aren't other open [pull requests](https://github.com/plone/volto/pulls) for the same change.
+- [ ] I followed the guidelines in [Contributing to Volto](https://6.docs.plone.org/volto/contributing/index.html).
+- [ ] I succesfully ran [code linting checks](https://6.docs.plone.org/volto/contributing/linting.html) on my changes locally.
+- [ ] I succesfully ran [unit tests](https://6.docs.plone.org/volto/contributing/testing.html) on my changes locally.
+- [ ] I succesfully ran [acceptance tests](https://6.docs.plone.org/volto/contributing/acceptance-tests.html) on my changes locally.
+- [ ] If needed, I added new tests for my changes.
+- [ ] If needed, I added [documentation](https://6.docs.plone.org/volto/contributing/documentation.html#narrative-documentation) for my changes, either in the Storybook or narrative documentation.
+- [ ] I included a [change log entry](https://6.docs.plone.org/contributing/index.html#contributing-change-log-label) in my commits.
+
+-----
+
+If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.
+
+Closes #

.github/actions/node_env_setup/action.yml

@@ -0,0 +1,50 @@
+name: Set up Node.js environment
+
+runs:
+  using: "composite"
+  steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js ${{ inputs.node-version }}
+      uses: actions/setup-node@v4
+      with:
+        node-version: ${{ inputs.node-version }}
+
+    - name: Enable corepack
+      shell: bash
+      run: npm i -g corepack@latest && corepack enable
+
+    - name: Get pnpm store directory
+      shell: bash
+      run: |
+        echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
+
+    - uses: actions/cache@v4
+      name: Setup pnpm cache
+      with:
+        path: ${{ env.STORE_PATH }}
+        key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+        restore-keys: |
+          ${{ runner.os }}-pnpm-store-
+
+    - name: Cache Cypress Binary
+      id: cache-cypress-binary
+      uses: actions/cache@v4
+      with:
+        path: ~/.cache/Cypress
+        key: binary-${{ inputs.node-version }}-${{ hashFiles('pnpm-lock.yaml') }}
+
+    - name: Install Volto dependencies
+      shell: bash
+      run: make install
+
+    - name: Install Cypress if not in cache
+      if: steps.cache-cypress-binary.outputs.cache-hit != 'true'
+      shell: bash
+      working-directory: packages/volto
+      run: make cypress-install
+
+inputs:
+  node-version:
+    description: 'Node.js version'
+    required: true

.github/boring-cyborg.yml

@@ -0,0 +1,140 @@
+# boring-cyborg.yml
+# https://probot.github.io/apps/boring-cyborg/
+
+##### Labeler ##########################################################################################################
+## Enable "labeler" for your PR that would add labels to PRs based on the paths that are modified in the PR.
+#labelPRBasedOnFilePath:
+#  # Add 'label1' to any changes within 'example' folder or any subfolders
+#  label1:
+#    - example/**/*
+#
+#  # Add 'label2' to any file changes within 'example2' folder
+#  label2:
+#    - example2/*
+#
+#  # Complex: Add 'area/core' label to any change within the 'core' package
+#  area/core:
+#    - src/core/*
+#    - src/core/**/*
+#
+#  # Add 'test' label to any change to *.spec.js files within the source dir
+#  test:
+#    - src/**/*.spec.js
+#
+# Various Flags to control behaviour of the "Labeler"
+#labelerFlags:
+#  # If this flag is changed to 'false', labels would only be added when the PR is first created and not when existing
+#  # PR is updated.
+#  # The default is 'true' which means the labels would be added when PR is updated even if they were removed by the user
+#  labelOnPRUpdates: true
+
+##### Reviewer #########################################################################################################
+# Enable "Reviewer" for your PR that would add reviewers to PRs based on the labels that exist on the PR.
+# You have the option to set a default reviewer that gets added to every PR, or you can omit that config variable to skip it.
+#addReviewerBasedOnLabel:
+  # add list of reviewers to add by default to all PRs
+#  defaultReviewers:
+#    - stevepiercy
+  # specify PR labels that you want to auto assign reviewers based on
+#  labels:
+#    label1:
+#      - tyler-mairose-sp
+#      - jordan-violet-sp
+#    label2:
+#      - kaxil
+
+##### Greetings ########################################################################################################
+# Comment to be posted to welcome users when they open their first PR
+firstPRWelcomeComment: >
+
+  > [!CAUTION]
+  > The Volto Team has suspended its review of new pull requests from first-time contributors until the [release of Plone 7](https://plone.org/download/release-schedule), which is preliminarily scheduled for the second quarter of 2026.
+  > [Read details](https://6.docs.plone.org/volto/contributing/index.html).
+  
+  Thanks for submitting your first pull request! You are awesome! :hugs:
+
+  If you haven't done so already, read
+  [Plone's Code of Conduct](https://plone.org/foundation/about/materials/foundation-resolutions/code-of-conduct),
+  [Contributing to Plone](https://6.docs.plone.org/contributing/index.html),
+  [First-time contributors](https://6.docs.plone.org/contributing/first-time.html), and
+  [Contributing to Volto](https://6.docs.plone.org/volto/contributing/index.html),
+  as this will greatly help the review process.
+
+  Welcome to the Plone community! :tada:
+
+# Comment to be posted to congratulate user on their first merged PR
+firstPRMergeComment: >
+  Congratulations on your first merged pull request in this project! :tada:
+
+  ![Congratulations](https://raw.githubusercontent.com/plone/documentation/fda4eadee4b0b71c4bcd0da739847444f74d3fc5/.github/images/congratulations.jpg)
+
+  <br>Thank you for contributing, we are very proud of you! :heart:
+
+# Comment to be posted to on first time issues
+firstIssueWelcomeComment: >
+  Thanks for opening your first issue here!
+  Your engagement is essential for open source projects, including Plone. :hugs:
+
+  <br>If you haven't done so already,
+  read [Plone's Code of Conduct](https://plone.org/foundation/about/materials/foundation-resolutions/code-of-conduct).
+  Also please follow the issue template, as it helps both you and other community members contribute more effectively.
+  
+  <br>If your issue is a feature request, others may raise its prominence through
+  [feature voting](https://github.com/plone/volto/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc%20).
+
+  <br>Welcome to the Plone community! :tada:
+
+###### IssueLink Adder #################################################################################################
+# Insert Issue (Jira/Github etc) link in PR description based on the Issue ID in PR title.
+#insertIssueLinkInPrDescription:
+#   # specify the placeholder for the issue link that should be present in the description
+#  descriptionIssuePlaceholderRegexp: "^Issue link: (.*)$"
+#  matchers:
+#    # you can have several matches - for different types of issues
+#    # only the first matching entry is replaced
+#    jiraIssueMatch:
+#      # specify the regexp of issue id that you can find in the title of the PR
+#      # the match groups can be used to build the issue id (${1}, ${2}, etc.).
+#      titleIssueIdRegexp: \[(AIRFLOW-[0-9]{4})\]
+#      # the issue link to be added. ${1}, ${2} ... are replaced with the match groups from the
+#      # title match (remember to use quotes)
+#      descriptionIssueLink: "[${1}](https://issues.apache.org/jira/browse/${1}/)"
+#    docOnlyIssueMatch:
+#      titleIssueIdRegexp: \[(AIRFLOW-X{4})\]
+#      descriptionIssueLink: "`Document only change, no JIRA issue`"
+#
+###### Title Validator #################################################################################################
+# Verifies if commit/PR titles match the regexp specified
+#verifyTitles:
+#  # Regular expression that should be matched by titles of commits or PR
+#  titleRegexp: ^\[AIRFLOW-[0-9]{4}\].*$|^\[AIRFLOW-XXXX\].*$
+#  # If set to true, it will always check the PR title (as opposed to the individual commits).
+#  alwaysUsePrTitle: true
+#  # If set to true, it will only check the commit in case there is a single commit.
+#  # In case of multiple commits it will check PR title.
+#  # This reflects the standard behaviour of Github that for `Squash & Merge` GitHub
+#  # uses the PR title rather than commit messages for the squashed commit ¯\_(ツ)_/¯
+#  # For single-commit PRs it takes the squashed commit message from the commit as expected.
+#  #
+#  # If set to false it will check all commit messages. This is useful when you do not squash commits at merge.
+#  validateEitherPrOrSingleCommitTitle: true
+#  # The title the GitHub status should appear from.
+#  statusTitle: "Title Validator"
+#  # A custom message to be displayed when the title passes validation.
+#  successMessage: "Validation successful!"
+#  # A custom message to be displayed when the title fails validation.
+#  # Allows insertion of ${type} (commit/PR), ${title} (the title validated) and ${regex} (the titleRegexp above).
+#  failureMessage: "Wrong ${type} title: ${title}"
+#
+###### PR/Branch Up-To-Date Checker ####################################################################################
+## Check if the branch is up to date with master when certain files are modified
+#checkUpToDate:
+#  # The default branch is "master", change the branch if you want to check against a different target branch
+#  targetBranch: master
+#  files:
+#  # File paths that you want to check for
+#  # In this example, it checks if the branch is up to date when alembic migrations are modified in the PR.
+#  # It helps avoid multiple heads in alembic migrations in a collaborative development project.
+#    - airflow/migrations/*
+#    - airflow/migrations/**/*
+#    - airflow/alembic.ini