python/release-tools

Issues

• Post-release-branch update of main fails to update a few things

  #45 opened 7 months ago by Yhg1s
  0

• run_release should regenerate configure after editing configure.ac.

  #126 opened 7 months ago by Yhg1s
  2

• Install optional dependencies during test stage

  #123 opened 7 months ago by sethmlarson
  2

• Separate builds for source and docs due to dependency differences

  #74 opened 8 months ago by sethmlarson
  1

• Add a type checker

  #114 opened 8 months ago by hugovk
  0

• Allow any release manager to build any release stream

  #111 opened 8 months ago by sethmlarson
  0

• Further automate build and release process

  #108 opened 8 months ago by sethmlarson
  0

• Move pip SBOM discovery to release-tools repository

  #91 opened 10 months ago by sethmlarson
  0

• Strip newline off "Tool Version" in SBOM creator metadata

  #90 opened 10 months ago by sethmlarson
  0

• Create some CI for linting and testing functionality

  #85 opened 10 months ago by sethmlarson
  0

• Issue with make regen-configure

  #83 opened a year ago by sethmlarson
  0

• Pin the cpython_autoconf container to a sha256 manifest

  #70 opened a year ago by sethmlarson
  0

• Rename `master` to `main`?

  #68 opened a year ago by hugovk
  1

• Automate builds of source and docs artifacts with GitHub Actions

  #66 opened a year ago by sethmlarson
  0

• Date and Release fields should be removed from prev_branch's whatsnew when creating new_branch's whatsnew

  #34 opened a year ago by zware
  2

• Add newly created branch to Azure Pipelines

  #56 opened a year ago by hugovk
  0

• Stop generating Sigstore disjoint verification materials (crt/sig)

  #55 opened a year ago by sethmlarson
  0

• ABI dump check needs to be added after branching

  #46 opened 2 years ago by encukou
  2

• The add_to_python.org fails for some windows versions

  #30 opened 2 years ago by pablogsal
  4

• The sigstore command on `add_to_pythondotorg.py` still asks for interactive input.

  #25 opened 2 years ago by pablogsal
  3

• Issues w/ Sigstore signing

  #21 opened 2 years ago by di
  7

• Include sha256 hashes of release downloads in announcement communications

  #16 opened 3 years ago by gpshead
  4

• Automation: point the source in new branches to the correct place

  #10 opened 4 years ago by pablogsal
  0