Automated publishing of packages to pub.dev


pub.dev adds support for automated publishing which supports publishing from the following sources: GitHub Actions, Google Cloud Build, anywhere else using a GCP service account.


Source:

PyPI introduces Trusted Publishing


PyPI coins the term 'Trusted Publishing' with support for packages published through GitHub Actions.


Source:

RubyGems adds support for Trusted Publishing


RubyGems adds support for Trusted Publishing for packages published through GitHub Actions.


Source:

JSR (the JavaScript Registry) adds support for Trusted Publishing


JSR adds support for Trusted Publishing for packages published through GitHub Actions.


Source:

PyPI expands Trusted Publisher Support


PyPI adds support for publishing packages through three additional providers: GitLab CI/CD, Google Cloud, and ActiveState.


Source:

crates.io adds support for Trusted Publishing


crates.io adds support for Trusted Publishing for packages published through GitHub Actions.


Source:

npm adds support for Trusted Publishing


npm adds support for Trusted Publishing for packages published through GitHub Actions and GitLab CI/CD.


Source:

Private Packagist adds support for Trusted Publishing


Private Packagist adds support for Trusted Publishing for packages published through GitHub Actions.


Source:

NuGet adds support for Trusted Publishing


nuget.org adds support for Trusted Publishing for packages published through GitHub Actions and GitLab CI/CD.


Source:

PyPI expands Trusted Publisher Support to GitLab Self-Managed and enables Pending Trusted Publishers for Organizations


Support for GitLab Self-Managed instances is now in beta, and it is now possible to pending Trusted Publisher at the Organization level which was previously only possible at the user level.


Source:

crates.io adds support for Trusted Publishing with GitLab CI/CD


crates.io now supports GitLab CI/CD in addition to GitHub Actions.


Source: