"Skip to main content\n Join us in Long Beach, CA starting May 13, 2026. Grab your ticket and discounted hotel today before they’re gone!  REGISTER FOR PYCON US!\nSearch PyPI\nSearch\n sadhiappan \nYour account\n Your projects\n Your organizations\n Account settings\n Publishing\nTrusted Publisher Management\n\nOpenID Connect (OIDC) provides a flexible, credential-free mechanism for delegating publishing authority for a PyPI package to a trusted third party service, like GitHub Actions.\n\nPyPI users and projects can use trusted publishers to automate their release processes, without needing to use API tokens or passwords.\n\nYou can read more about trusted publishers and how to use them here.\n\nManage publishers\nProjects with active publishers\n\nNo publishers are currently configured. Publishers for existing projects can be added in the publishing configuration for each individual project.\n\nPending publishers\nPending project name\tPublisher\tDetails\t\nms365-toolkit\tGitHub\t\nRepository: sadhiappan/ms365-toolkit\nWorkflow: release.yml\nEnvironment name: (Any)\n\tRemove\nAdd a new pending publisher\n\nYou can use this page to register \"pending\" trusted publishers.\n\nThese publishers behave similarly to trusted publishers registered against specific projects, except that they allow users to create the project if it doesn't already exist. Once the project is created, the \"pending\" publisher becomes an ordinary trusted publisher. You can read more about \"pending\" and ordinary trusted publishers here.\n\nConfiguring a \"pending\" publisher for a project name does not reserve that name. Until the project is created, any other user may create it, including via their own \"pending\" publisher.\n\nGitHub\nGitLab\nGoogle\nActiveState\n\nRead more about GitHub Actions' OpenID Connect support here.\n\nPyPI Project Name (required)\n\nThe project that will be created on PyPI when this publisher is used\n\nOwner (required)\n\nThe GitHub organization name or GitHub username that owns the repository\n\nRepository name (required)\n\nThe name of the GitHub repository that contains the publishing workflow\n\nWorkflow name (required)\n\nThe filename of the publishing workflow. This file should exist in the .github/workflows/ directory in the repository configured above.\n\nEnvironment name (optional)\n\nThe name of the GitHub Actions environment that the above workflow uses for publishing. This should be configured under the repository's settings. While not required, a dedicated publishing environment is strongly encouraged, especially if y"