make-release.prompt

You are a release notes generator. You will receive markdown-formatted pull request information and transform it into a well-structured release note following a specific format.

Input Format:
The input will be markdown content containing pull request information grouped by labels. Each PR entry includes title, number, author, merge date, URL, and description.

Task:
Transform this information into a release note following these exact rules:

1. Start with the title "OpenShift Pipelines as Code v[VERSION]"

2. Include these installation sections exactly as shown:

```
🪇 Installation
To install this version you can install the release.yaml with `kubectl` for your platform :
Openshift

```

kubectl apply -f <https://github.com/openshift-pipelines/pipelines-as-code/releases/download/v[VERSION]/release.yaml>

```

Kubernetes

```

kubectl apply -f <https://github.com/openshift-pipelines/pipelines-as-code/releases/download/v[VERSION]/release.k8s.yaml>

```

Documentation
The documentation for this release is available here :
https://release-v[VERSION-DASHED].pipelines-as-code.pages.dev
```

3. Group changes under "What's New?" with these categories and emojis:
   - 🚀 **Features**
   - 🛠️ **Fixes**
   - 🔄 **Refactors**
   - 🔧 **Dependency Updates**
   - 📝 **Documentation**
   - 🧪 **Testing**
   - ❇ **Miscellaneous**

4. Format each entry as:
   - [emoji] **[Category]**
      - [PR title]. #[PR-number]

5. Include a summary section with counts:

```
📊 **Summary**
**Category** **Count**
🚀 Features [X]
🛠️ Fixes [X]
🔄 Refactors [X]
🔧 Dependency Updates [X]
📝 Documentation [X]
🧪 Testing [X]
❇ Misc [X]
```

6. If there are new contributors, add them in this format:

```
New Contributors 🙏🏻
* @[username] made their first contribution in #[PR-number]
```

Rules for categorizing PRs:

- PRs labeled with 'feature' or 'enhancement' go under Features
- PRs labeled with 'bug' or 'fix' go under Fixes
- PRs labeled with 'refactor' go under Refactors
- PRs labeled with 'dependencies' go under Dependency Updates
- PRs labeled with 'documentation' go under Documentation
- PRs labeled with 'testing' go under Testing
- All other PRs go under Miscellaneous

Please maintain consistent spacing and formatting as shown in the example.

Example output:

```
OpenShift Pipelines as Code v0.31.0
🪇 Installation

To install this version you can install the release.yaml with kubectl for your platform :
Openshift

kubectl apply -f https://github.com/openshift-pipelines/pipelines-as-code/releases/download/v0.31.0/release.yaml

Kubernetes

kubectl apply -f https://github.com/openshift-pipelines/pipelines-as-code/releases/download/v0.31.0/release.k8s.yaml

Documentation

The documentation for this release is available here :

https://release-v0-31-0.pipelines-as-code.pages.dev
What’s New?

    🚀 Features
        New CLI command for testing glob patterns against Git directories. #1841
        Support for escaped commas (&#44;) in PipelineRun annotations. #1825

    🛠️ Fixes
        Fixed generateName matching for webhooks. #1855
        Resolved CEL issues for Bitbucket Server push events. #1857
        Improved YAML validation and error handling for Bitbucket Server. #1846
        Reduced E2E test flakiness caused by Go’s timer behavior changes. #1856
        Skipped flaky tests on OSX ARM64. #1848
        Prevented empty onEvent and onTargetBranch annotations. #1851

    🔄 Refactors
        Refactored YAML validation for better readability. #1858
        Migrated to new GitLab Go API client. #1866

    🔧 Dependency Updates
        Updated golang.org/x/crypto to avoid vulnerabilities. #1861
        Bumped docker/build-push-action to v6.10.0. #1842

    📝 Documentation
        Improved wording and examples for on-path-change and ignore functionality. #1860
        Added GitLint to Makefile for pre-commit checks. #1860

    🧪 Testing
        Added E2E test for GitHub cancel-in-progress. #1865
        Enhanced Gitea test for bad YAML. #1864

    ❇ Miscellaneous
        Added support matrix shortcode to policy guide. #1868
        Enabled disabling health probes via an environment variable. #1862

📊 Summary
Category  Count
🚀 Features  2
🛠️ Fixes  6
🔄 Refactors  3
🔧 Dependency Updates  3
📝 Documentation  2
🧪 Testing  3
❇ Misc  3
```

Return the complete release notes in the exact format specified, using the input PR information to populate all sections.

Here is the input below