chore(maintenance): align CI matrices and repository templates

.github/DISCUSSION_TEMPLATE/rfcs.yml → .github/DISCUSSION_TEMPLATE/rfcs-request-for-comments.yml

@@ -25,6 +25,9 @@ body:
         - JMESPath
         - Batch Processing
         - Validation
+        - Kafka
+        - Data Masking
+        - Signer
         - Commons
         - Automation
         - Governance
@@ -109,4 +112,4 @@ body:
     attributes:
       label: Future readers
       description: Please not edit this field
-      value: "Please react with 👍 and your use case to help us understand customer demand."
+      value: "Please react with 👍 and your use case to help us understand customer demand."

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,8 @@
 name: Bug report
 description: Report a reproducible bug to help us improve
 title: "Bug: <TITLE>"
-labels: ["bug", "triage"]
+labels: ["triage"]
+type: Bug
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/documentation_improvements.yml

@@ -1,7 +1,8 @@
 name: Documentation improvements
 description: Suggest a documentation update to improve everyone's experience
 title: "Docs: <TITLE>"
-labels: ["documentation", "triage"]
+labels: ["triage"]
+type: Task
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,7 +1,8 @@
 name: Feature request
 description: Suggest an idea for Powertools for AWS Lambda
 title: "Feature request: <TITLE>"
-labels: ["feature-request", "triage"]
+labels: ["triage"]
+type: Enhancement
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/maintenance.yml

@@ -1,7 +1,8 @@
 name: Maintenance
 description: Suggest an activity to help address tech debt, governance, and anything internal
 title: "Maintenance: <TITLE>"
-labels: ["internal", "triage"]
+labels: ["triage"]
+type: Task
 body:
   - type: markdown
     attributes:

.github/workflows/on_pr_updates.yml

@@ -12,8 +12,8 @@ name: PR requirements
 
 # NOTES
 #
-# PR requirements are checked async in on_opened_pr.yml and enforced here synchronously
-# due to limitations in GH API.
+# Organization-level checks evaluate PR requirements asynchronously; this workflow enforces
+# the resulting do-not-merge label synchronously due to limitations in the GitHub API.
 
 on:
   pull_request:
@@ -32,4 +32,4 @@ jobs:
         if: contains(github.event.pull_request.labels.*.name, 'do-not-merge')
         run: |
           echo "This PR does not meet minimum requirements (check PR comments)."
-          exit 1
+          exit 1

.github/workflows/quality_check.yml

@@ -21,17 +21,22 @@ jobs:
     strategy:
       matrix:
         version: [22, 24]
+        # packages/testing is private and intentionally excluded from this publishable package matrix.
         workspace: [
           "packages/batch",
           "packages/commons",
+          "packages/data-masking",
           "packages/event-handler",
           "packages/idempotency",
           "packages/jmespath",
+          "packages/kafka",
           "packages/logger",
           "packages/tracer",
           "packages/parser",
           "packages/parameters",
-          "packages/metrics"
+          "packages/metrics",
+          "packages/signer",
+          "packages/validation"
         ]
       fail-fast: false
     steps:

.github/workflows/reusable-run-linting-check-and-unit-tests.yml

@@ -41,6 +41,7 @@ jobs:
     strategy:
       matrix:
         version: [22, 24]
+        # packages/testing is private and intentionally excluded from this publishable package matrix.
         workspace: [
           "packages/batch",
           "packages/commons",
@@ -54,7 +55,8 @@ jobs:
           "packages/parameters",
           "packages/validation",
           "packages/metrics",
-          "packages/kafka"
+          "packages/kafka",
+          "packages/signer"
         ]
       fail-fast: false
     steps:

CONTRIBUTING.md

@@ -16,7 +16,7 @@
 - [Licensing](#licensing)
 
 <!-- markdownlint-disable MD013 -->
-Thank you for your interest in contributing to our project. Whether it's a [bug report](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=type%2Fbug%2Ctriage&projects=aws-powertools%2F7&template=bug_report.yml&title=Bug%3A+TITLE), [new feature](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=type%2Ffeature-request%2Ctriage&projects=aws-powertools%2F7&template=feature_request.yml&title=Feature+request%3A+TITLE), [correction](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new/choose), or [additional documentation](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=area%2Fdocumentation%2Ctriage&projects=aws-powertools%2F7&template=documentation_improvements.yml&title=Docs%3A+TITLE), we greatly value feedback and contributions from our community.
+Thank you for your interest in contributing to our project. Whether it's a [bug report](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=triage&projects=aws-powertools%2F7&template=bug_report.yml&title=Bug%3A+TITLE), [new feature](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=triage&projects=aws-powertools%2F7&template=feature_request.yml&title=Feature+request%3A+TITLE), [correction](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new/choose), or [additional documentation](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=triage&projects=aws-powertools%2F7&template=documentation_improvements.yml&title=Docs%3A+TITLE), we greatly value feedback and contributions from our community.
 <!-- markdownlint-enable MD013 -->
 
 We encourage contributions from the community and we will work with contributors to merge their pull requests.

docs/features/metrics.md

@@ -382,7 +382,7 @@ If it's a cold start invocation, this feature will:
 
 This has the advantage of keeping cold start metric separate from your application metrics, where you might have unrelated dimensions.
 
-!!! info "We do not emit 0 as a value for the ColdStart metric for cost-efficiency reasons. [Let us know](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=feature-request%2C+triage&template=feature_request.md&title=) if you'd prefer a flag to override it."
+!!! info "We do not emit 0 as a value for the ColdStart metric for cost-efficiency reasons. [Let us know](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=triage&template=feature_request.yml&title=) if you'd prefer a flag to override it."
 
 #### Setting function name
 

docs/roadmap.md

@@ -98,7 +98,7 @@ To ensure we are attracting tomorrow's customers as well as new contributors to
 
 ### Missing something?
 
-You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-typescript/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc++label%3Atype%2Ffeature-request+), leaving a comment on what use cases it could unblock for you, and by joining our discussions on GitHub.
+You can help us prioritize by [upvoting existing feature requests](https://github.com/aws-powertools/powertools-lambda-typescript/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+type%3AEnhancement), leaving a comment on what use cases it could unblock for you, and by joining our discussions on GitHub.
 
 [![GitHub Discussions](https://img.shields.io/badge/GitHub-Discussions-181717.svg?logo=github)](https://github.com/aws-powertools/powertools-lambda-typescript/discussions)
 
@@ -140,9 +140,9 @@ graph LR
 
 Our end-to-end mechanism follows four major steps:
 
-- **Feature Request**. Ideas start with a [feature request](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=type%2Ffeature-request%2Ctriage&template=feature_request.yml&title=Feature+request%3A+TITLE){target="_blank"} to outline their use case at a high level. For complex use cases, maintainers might ask for/write a RFC.
+- **Feature Request**. Ideas start with a [feature request](https://github.com/aws-powertools/powertools-lambda-typescript/issues/new?assignees=&labels=triage&template=feature_request.yml&title=Feature+request%3A+TITLE){target="_blank"} to outline their use case at a high level. For complex use cases, maintainers might ask for/write a RFC.
     - Maintainers review requests based on [project tenets](index.md#tenets){target="_blank"}, customers reaction (👍), and use cases.
-- **Request-for-comments (RFC)**. Design proposals use our [RFC template](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/new?category=rfcs){target="_blank"} to describe its implementation, challenges, developer experience, dependencies, and alternative solutions.
+- **Request-for-comments (RFC)**. Design proposals use our [RFC template](https://github.com/aws-powertools/powertools-lambda-typescript/discussions/new?category=rfcs-request-for-comments){target="_blank"} to describe its implementation, challenges, developer experience, dependencies, and alternative solutions.
     - This helps refine the initial idea with community feedback before a decision is made.
 - **Decision**. After carefully reviewing and discussing them, maintainers make a final decision on whether to start implementation, defer or reject it, and update everyone with the next steps.
 - **Implementation**. For approved features, maintainers give priority to the original authors for implementation unless it is a sensitive task that is best handled by maintainers.