ci(labels): switch automation and templates to the migrated label set (#11323)

Author: mergify[bot]

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: '🐛 Bug report'
 description: Create a report to help us improve
 title: 'bug: '
-labels: [C-bug, S-needs-triage]
+type: Bug
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/devops_report.yml

@@ -2,7 +2,8 @@
 name: '🚦 DevOps Report'
 description: Issues related to the Zebra build, test, or release process.
 title: 'devops: '
-labels: [A-devops, C-bug, S-needs-triage]
+labels: [devops]
+type: Bug
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -2,7 +2,7 @@
 name: "🚧 Change request"
 description: Suggest a feature or change for this project
 title: 'feature: '
-labels: [C-enhancement, S-needs-triage]
+type: Feature
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/private_security_issue.yml

@@ -2,7 +2,8 @@
 name: '🔓 Private Security Issue'
 description: Zebra team use only
 title: 'Security Issue #NNN'
-labels: [C-security, S-needs-triage]
+labels: [security]
+type: Bug
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/release.md

@@ -2,7 +2,8 @@
 name: "🚀 Zebra Release"
 about: "Zebra team use only"
 title: "Publish next Zebra release: (version)"
-labels: "A-release, C-exclude-from-changelog, P-Medium :zap:"
+labels: "A-release"
+type: Task
 assignees: ""
 ---
 

.github/ISSUE_TEMPLATE/usability_testing_plan.md

@@ -2,7 +2,7 @@
 name: "📋 Usability Testing Plan"
 about: Create a Usability Testing Plan
 title: "Usability Testing Plan"
-labels: C-research
+type: Task
 assignees: ""
 ---
 

.github/ISSUE_TEMPLATE/zcashd_dependencies.yml

@@ -2,7 +2,7 @@
 name: "Upgrade zcashd dependencies"
 description: "Specific steps for upgrading dependencies shared with zcashd. Zebra developers only."
 title: 'Upgrade dependencies for zcashd (version)'
-labels: [A-dependencies, A-script, S-needs-triage]
+type: Task
 body:
   - type: markdown
     attributes:

.github/PULL_REQUEST_TEMPLATE/hotfix-release-checklist.md

@@ -1,8 +1,8 @@
 ---
 name: "Hotfix Release Checklist Template"
 about: "Checklist to create and publish a hotfix Zebra release"
-title: "Release Zebra (version)"
-labels: "A-release, C-exclude-from-changelog, P-Critical :ambulance:"
+title: "release: Zebra (version)"
+labels: "A-release"
 assignees: ""
 ---
 
@@ -14,7 +14,6 @@ A hotfix release should only be created when a bug or critical issue is discover
       for example: `hotfix-v2.3.1` - this needs to be different to the tag name
 - [ ] Make the required changes
 - [ ] Create a hotfix release PR by adding `&template=hotfix-release-checklist.md` to the comparing url ([Example](https://github.com/ZcashFoundation/zebra/compare/bump-v1.0.0?expand=1&template=hotfix-release-checklist.md)).
-- [ ] Add the `C-exclude-from-changelog` label so that the PR is omitted from the next release changelog
 - [ ] Add the `A-release` tag to the release pull request in order for the `check-no-git-dependencies` to run.
 - [ ] Add the `do-not-merge` tag to prevent Mergify from merging, since after PR approval the
       release is done from the branch itself.

.github/PULL_REQUEST_TEMPLATE/release-checklist-legacy.md

@@ -1,8 +1,8 @@
 ---
 name: "Legacy Release Checklist Template"
 about: "Manual fallback checklist to create and publish a Zebra release"
-title: "Release Zebra (version)"
-labels: "A-release, C-exclude-from-changelog, P-Critical :ambulance:"
+title: "release: Zebra (version)"
+labels: "A-release"
 assignees: ""
 ---
 
@@ -75,7 +75,6 @@ fastmod --fixed-strings '1.58' '1.65'
       for example: `bump-v1.0.0` - this needs to be different to the tag name
 - [ ] Create a release PR by adding `&template=release-checklist-legacy.md` to the comparing url ([Example](https://github.com/ZcashFoundation/zebra/compare/bump-v1.0.0?expand=1&template=release-checklist-legacy.md)).
 - [ ] Freeze the [`batched` queue](https://dashboard.mergify.com/github/ZcashFoundation/repo/zebra/queues) using Mergify.
-- [ ] Mark all the release PRs as `Critical` priority, so they go in the `urgent` Mergify queue.
 - [ ] Mark all non-release PRs with `do-not-merge`, because Mergify checks approved PRs against every commit, even when a queue is frozen.
 - [ ] Add the `A-release` tag to the release pull request in order for the `check-no-git-dependencies` to run.
 

.github/copilot-instructions.md

@@ -96,7 +96,6 @@ When the PR adds abstraction, flags, generics, or refactors:
 - Changelogs are generated by [changie](https://changie.dev) from `.changes/`: never edit `CHANGELOG.md` or a crate's `CHANGELOG.md` by hand
 - User-visible changes need a change fragment: `changie new -j zebrad -k Added -b "..."`
 - Library-consumer-visible changes need one fragment per affected crate: `changie new -j zebra-chain -j zebra-state -k breaking -b "..."`
-- PR labels must match the intended changelog category (`C-bug`, `C-feature`, `C-security`, etc.)
 - PR title and branch commits follow conventional commits (merged to main with a merge commit, so branch commits are preserved)
 
 ## Extra Scrutiny Areas