Update libp2p.yml - add yiannisbot

[yiannisbot]

Summary

Get added to the repo so that I can see non-public advisories and such.

Why do you need this?

What else do we need to know?

DRI: myself or one of the admins

Reviewer's Checklist

• It is clear where the request is coming from (if unsure, ask)
• All the automated checks passed
• The YAML changes reflect the summary of the request
• The Terraform plan posted as a comment reflects the summary of the request

[github-actions]

The following access changes will be introduced as a result of applying the plan:

Access Changes

User yiannisbot:
  - will have the permission to go-libp2p-kad-dht change from maintain to admin
  - will gain admin permission to .github
  - will gain admin permission to awesome-libp2p
  - will gain admin permission to blog
  - will gain admin permission to community
  - will gain admin permission to cpp-libp2p
  - will gain admin permission to cs-libp2p-crypto
  - will gain admin permission to cs-libp2p-io
  - will gain admin permission to cs-libp2p-peer
  - will gain admin permission to cs-libp2p-protocol
  - will gain admin permission to cs-libp2p-record
  - will gain admin permission to cs-libp2p-utils
  - will gain admin permission to demo-multi-lang
  - will gain admin permission to developer-meetings
  - will gain admin permission to devgrants
  - will gain admin permission to dht-hardening
  - will gain admin permission to dht-tracer
  - will gain admin permission to dht-tracer-archived
  - will gain admin permission to dht-tracer1
  - will gain admin permission to dht-utils
  - will gain admin permission to dht-vis-v0
  - will gain admin permission to docs
  - will gain admin permission to docs-old
  - will gain admin permission to fclibp2p-zhi
  - will gain admin permission to go-buffer-pool
  - will gain admin permission to go-cidranger
  - will gain admin permission to go-composable-routing
  - will gain admin permission to go-doh-resolver
  - will gain admin permission to go-flow-metrics
  - will gain admin permission to go-libp2p
  - will gain admin permission to go-libp2p-asn-util
  - will gain admin permission to go-libp2p-backoff
  - will gain pull permission to go-libp2p-certbot
  - will gain admin permission to go-libp2p-consensus
  - will gain admin permission to go-libp2p-daemon
  - will gain admin permission to go-libp2p-gorpc
  - will gain admin permission to go-libp2p-gostream
  - will gain admin permission to go-libp2p-holepunch-test
  - will gain admin permission to go-libp2p-http
  - will gain admin permission to go-libp2p-introspector
  - will gain admin permission to go-libp2p-kbucket
  - will gain admin permission to go-libp2p-mplex
  - will gain admin permission to go-libp2p-pubsub
  - will gain admin permission to go-libp2p-pubsub-router
  - will gain admin permission to go-libp2p-pubsub-tracer
  - will gain admin permission to go-libp2p-raft
  - will gain admin permission to go-libp2p-record
  - will gain admin permission to go-libp2p-relay-daemon
  - will gain admin permission to go-libp2p-rendezvous
  - will gain admin permission to go-libp2p-routing-helpers
  - will gain admin permission to go-libp2p-slog
  - will gain admin permission to go-libp2p-testing
  - will gain admin permission to go-libp2p-websocket-star-rendezvous
  - will gain admin permission to go-libp2p-xor
  - will gain admin permission to go-mplex
  - will gain admin permission to go-msgio
  - will gain admin permission to go-nat
  - will gain admin permission to go-netroute
  - will gain admin permission to go-reuseport
  - will gain admin permission to go-routing-language
  - will gain admin permission to go-smart-record
  - will gain admin permission to go-socket-activation
  - will gain admin permission to go-udp-transport
  - will gain admin permission to go-yamux
  - will gain admin permission to gossipsub-hardening
  - will gain admin permission to haskell-p2pcat
  - will gain admin permission to hydra-booster
  - will gain admin permission to interface-libp2p
  - will gain admin permission to interop
  - will gain pull permission to iptoasn
  - will gain admin permission to js-libp2p
  - will gain admin permission to js-libp2p-amino-dht-bootstrapper
  - will gain admin permission to js-libp2p-cms
  - will gain admin permission to js-libp2p-daemon
  - will gain admin permission to js-libp2p-daemon-client
  - will gain admin permission to js-libp2p-delegated-content-routing
  - will gain admin permission to js-libp2p-delegated-peer-routing
  - will gain admin permission to js-libp2p-examples
  - will gain admin permission to js-libp2p-nat-mngr
  - will gain admin permission to js-libp2p-pubsub-peer-discovery
  - will gain admin permission to js-libp2p-rendezvous
  - will gain admin permission to js-libp2p-udp
  - will gain admin permission to js-libp2p-udt
  - will gain admin permission to js-libp2p-utp
  - will gain admin permission to js-p2pcat
  - will gain admin permission to js-peer-id
  - will gain admin permission to jvm-libp2p
  - will gain admin permission to libp2p
  - will gain admin permission to notes
  - will gain admin permission to npm-go-libp2p-dep
  - will gain admin permission to observation-deck
  - will gain admin permission to observer-toolkit
  - will gain admin permission to projects
  - will gain admin permission to pull-mplex
  - will gain admin permission to py-libp2p
  - will gain admin permission to py-libp2p-slog
  - will gain admin permission to py-libp2p-xor
  - will gain admin permission to research-pubsub
  - will gain admin permission to rust-libp2p
  - will gain admin permission to rust-yamux
  - will gain admin permission to specs
  - will gain admin permission to team-mgmt
  - will gain admin permission to test-plans
  - will gain admin permission to website
  - will gain admin permission to website-new
  - will gain admin permission to xtp
  - will gain admin permission to zeroconf

[github-actions]

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

libp2p

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # github_team_membership.this["w3dt-stewards:yiannisbot"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "4657013"
      + username = "yiannisbot"
    }

Plan: 1 to add, 0 to change, 0 to destroy.