Unarchive py-ipld-dag and Update Repository Configuration

[seetadev]

Summary

We would like to take on maintenance of the py-ipld-dag repository and unarchive it to restore active development.

This is part of the ongoing effort to stabilize and modernize the Python libp2p dependency stack.

I’ve applied configuration defaults based on other active Python repositories in the org. Please let me know if anything should be adjusted.

Why do you need this?

We are actively maintaining py-multiaddr, which depends on py-cid, which in turn depends on py-ipld-dag.

Although we have access to the PyPI project, the GitHub repository being archived prevents:

• Opening and merging PRs
• Updating CI workflows
• Managing issues
• Coordinating releases across the dependency chain

Unarchiving py-ipld-dag is necessary to maintain a clean and sustainable release process for the Python libp2p ecosystem.

What changes were made?

• Unarchived the repository (archived: false)

• Set visibility to public

• Configured default branch to master

• Enabled secret_scanning and secret_scanning_push_protection

• Added appropriate team access:

  • Python Team (admin)

• github-mgmt stewards (pull)

• Added web3-bot with push access

• Updated repository description

• Set repository topics (cid, python)

• Applied standard merge commit configurations

These reflect defaults used in other maintained Python ecosystem repositories.

What else do we need to know?

DRI: myself

@acul71
@pacrob

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 achingbrain:
  - will gain admin permission to py-ipld-dag
User acul71:
  - will gain push permission to py-ipld-dag
User aschmahmann:
  - will gain admin permission to py-ipld-dag
User biglep:
  - will gain admin permission to py-ipld-dag
User daviddias:
  - will gain admin permission to py-ipld-dag
User dhruvbaldawa:
  - will gain admin permission to py-ipld-dag
User galargh:
  - will gain admin permission to py-ipld-dag
User guseggert:
  - will gain admin permission to py-ipld-dag
User jbenet:
  - will gain admin permission to py-ipld-dag
User jorropo:
  - will gain admin permission to py-ipld-dag
User kubuxu:
  - will gain admin permission to py-ipld-dag
User laurentsenta:
  - will gain admin permission to py-ipld-dag
User lidel:
  - will gain admin permission to py-ipld-dag
User pacrob:
  - will gain push permission to py-ipld-dag
User rvagg:
  - will gain push permission to py-ipld-dag
User seetadev:
  - will gain push permission to py-ipld-dag
User stebalien:
  - will gain admin permission to py-ipld-dag
User vmx:
  - will gain admin permission to py-ipld-dag
User warpfork:
  - will gain admin permission to py-ipld-dag
User web3-bot:
  - will gain push permission to py-ipld-dag
User whyrusleeping:
  - will gain admin permission to py-ipld-dag
User willscott:
  - will gain pull permission to py-ipld-dag

[github-actions]

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

Terraform plans

ipld

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

Terraform will perform the following actions:

  # github_repository.this["py-ipld-dag"] will be updated in-place
  ~ resource "github_repository" "this" {
      ~ archived                    = true -> false
        id                          = "py-ipld-dag"
        name                        = "py-ipld-dag"
      + web_commit_signoff_required = false
        # (34 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # github_team_repository.this["python team:py-ipld-dag"] will be created
  + resource "github_team_repository" "this" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "push"
      + repository = "py-ipld-dag"
      + team_id    = "2474599"
    }

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