add [email protected] to distributors-announce list

[pacoxu]

Fixes https://github.com/kubernetes/committee-security-response/issues/180

I add all information in the issue description.

[pacoxu]

/cc @kubernetes/security-response-committee

[k8s-ci-robot]

@pacoxu: GitHub didn't allow me to request PR reviews from the following users: kubernetes/security-response-committee.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @kubernetes/security-response-committee

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pacoxu]

/cc @ritazh @micahhausler

[pacoxu]

ack

[pacoxu]

/cc @justaugustus

[ritazh]

@enj PTAL

[justaugustus]

@kubernetes/security-response-committee – Bump for review.

I'm not part of the SRC, so: /uncc

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pacoxu]

@kubernetes/security-response-committee – Bump for review.

/remove-lifecycle stale

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pacoxu Once this PR has been reviewed and has the lgtm label, please assign micahhausler for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• groups/committee-security-response/OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[pacoxu]

/assign @enj Any action items that I can do for this?

[pacoxu]

@enj @kubernetes/security-response-committee any update on this progress? ACK.