npm-sampo-v0.19.0

Minor changes

• 10f39d5 In PHP (Packagist) projects, added support for private registries. Packages resolved through a private or alternative Composer registry (a type: "composer" repository in composer.json, or packagist.org disabled) no longer have their already-published check run against public Packagist. As private Composer registries (Private Packagist, Satis) stay VCS-based, sampo publish defers to the git-tag push that drives the registry update. — Thanks @goulvenclech!
• 2f56c94 In JavaScript/TypeScript (npm) projects, added support for private registries. sampo publish now authenticates its check for already-published versions with NPM_TOKEN or NODE_AUTH_TOKEN, falling back to your .npmrc when neither is set. — Thanks @goulvenclech!
• 55c5960 In Elixir (Hex) projects, added support for private organisations. For packages that declare an organization in their mix.exs package configuration, sampo publish now checks the organisation's repository for already-published versions and authenticates that check with HEX_API_KEY. — Thanks @goulvenclech!
• 53aacb9 In Cargo (Rust) projects, added support for alternative and private registries, and fixed crates that publish solely to an alternative registry (publish = ["my-registry"]) being wrongly marked as non-publishable. sampo publish now checks whether a version already exists on the target registry using your Cargo registry configuration and credentials. — Thanks @goulvenclech!
• 7239416 In Python (PyPI) projects, added support for private indexes. For packages that declare a uv index with a publish-url in pyproject.toml, sampo publish now routes the upload to that index via uv publish --index, which resolves the upload URL, credentials, and already-published checks from your uv configuration. — Thanks @goulvenclech!

Patch changes

• Updated dependencies: sampo-core (Cargo)@0.15.0

cargo-sampo-v0.19.0

Minor changes

• 10f39d5 In PHP (Packagist) projects, added support for private registries. Packages resolved through a private or alternative Composer registry (a type: "composer" repository in composer.json, or packagist.org disabled) no longer have their already-published check run against public Packagist. As private Composer registries (Private Packagist, Satis) stay VCS-based, sampo publish defers to the git-tag push that drives the registry update. — Thanks @goulvenclech!
• 2f56c94 In JavaScript/TypeScript (npm) projects, added support for private registries. sampo publish now authenticates its check for already-published versions with NPM_TOKEN or NODE_AUTH_TOKEN, falling back to your .npmrc when neither is set. — Thanks @goulvenclech!
• 55c5960 In Elixir (Hex) projects, added support for private organisations. For packages that declare an organization in their mix.exs package configuration, sampo publish now checks the organisation's repository for already-published versions and authenticates that check with HEX_API_KEY. — Thanks @goulvenclech!
• 53aacb9 In Cargo (Rust) projects, added support for alternative and private registries, and fixed crates that publish solely to an alternative registry (publish = ["my-registry"]) being wrongly marked as non-publishable. sampo publish now checks whether a version already exists on the target registry using your Cargo registry configuration and credentials. — Thanks @goulvenclech!
• 7239416 In Python (PyPI) projects, added support for private indexes. For packages that declare a uv index with a publish-url in pyproject.toml, sampo publish now routes the upload to that index via uv publish --index, which resolves the upload URL, credentials, and already-published checks from your uv configuration. — Thanks @goulvenclech!

Patch changes

• Updated dependencies: sampo-core (Cargo)@0.15.0

cargo-sampo-github-bot-v0.4.9

Patch changes

• Updated dependencies: sampo-core (Cargo)@0.15.0

cargo-sampo-github-action-v0.17.0

Minor changes

• 10f39d5 In PHP (Packagist) projects, added support for private registries. Packages resolved through a private or alternative Composer registry (a type: "composer" repository in composer.json, or packagist.org disabled) no longer have their already-published check run against public Packagist. As private Composer registries (Private Packagist, Satis) stay VCS-based, sampo publish defers to the git-tag push that drives the registry update. — Thanks @goulvenclech!
• 2f56c94 In JavaScript/TypeScript (npm) projects, added support for private registries. sampo publish now authenticates its check for already-published versions with NPM_TOKEN or NODE_AUTH_TOKEN, falling back to your .npmrc when neither is set. — Thanks @goulvenclech!
• 55c5960 In Elixir (Hex) projects, added support for private organisations. For packages that declare an organization in their mix.exs package configuration, sampo publish now checks the organisation's repository for already-published versions and authenticates that check with HEX_API_KEY. — Thanks @goulvenclech!
• 53aacb9 In Cargo (Rust) projects, added support for alternative and private registries, and fixed crates that publish solely to an alternative registry (publish = ["my-registry"]) being wrongly marked as non-publishable. sampo publish now checks whether a version already exists on the target registry using your Cargo registry configuration and credentials. — Thanks @goulvenclech!
• 7239416 In Python (PyPI) projects, added support for private indexes. For packages that declare a uv index with a publish-url in pyproject.toml, sampo publish now routes the upload to that index via uv publish --index, which resolves the upload URL, credentials, and already-published checks from your uv configuration. — Thanks @goulvenclech!

Patch changes

• Updated dependencies: sampo-core (Cargo)@0.15.0

cargo-sampo-core-v0.15.0

Minor changes

• 10f39d5 In PHP (Packagist) projects, added support for private registries. Packages resolved through a private or alternative Composer registry (a type: "composer" repository in composer.json, or packagist.org disabled) no longer have their already-published check run against public Packagist. As private Composer registries (Private Packagist, Satis) stay VCS-based, sampo publish defers to the git-tag push that drives the registry update. — Thanks @goulvenclech!
• 2f56c94 In JavaScript/TypeScript (npm) projects, added support for private registries. sampo publish now authenticates its check for already-published versions with NPM_TOKEN or NODE_AUTH_TOKEN, falling back to your .npmrc when neither is set. — Thanks @goulvenclech!
• 55c5960 In Elixir (Hex) projects, added support for private organisations. For packages that declare an organization in their mix.exs package configuration, sampo publish now checks the organisation's repository for already-published versions and authenticates that check with HEX_API_KEY. — Thanks @goulvenclech!
• 53aacb9 In Cargo (Rust) projects, added support for alternative and private registries, and fixed crates that publish solely to an alternative registry (publish = ["my-registry"]) being wrongly marked as non-publishable. sampo publish now checks whether a version already exists on the target registry using your Cargo registry configuration and credentials. — Thanks @goulvenclech!
• 7239416 In Python (PyPI) projects, added support for private indexes. For packages that declare a uv index with a publish-url in pyproject.toml, sampo publish now routes the upload to that index via uv publish --index, which resolves the upload URL, credentials, and already-published checks from your uv configuration. — Thanks @goulvenclech!

npm-sampo-v0.18.1

Patch changes

• 1ee9aa2 Fixed sampo publish creating a spurious git tag and GitHub release for non-publishable, versionless packages (workspace containers and other packages marked as non-publishable without a declared version). Non-publishable but versioned packages are still tagged as before. — Thanks @goulvenclech!
• 9584dc7 Changed sampo update to an optional self-update Cargo feature (enabled by default) so Sampo can be packaged for more package managers that handle updates themselves. Disable it with --no-default-features. — Thanks @nartsisss for your first contribution 🎉!
• Updated dependencies: sampo-core (Cargo)@0.14.1

cargo-sampo-v0.18.1

Patch changes

• 1ee9aa2 Fixed sampo publish creating a spurious git tag and GitHub release for non-publishable, versionless packages (workspace containers and other packages marked as non-publishable without a declared version). Non-publishable but versioned packages are still tagged as before. — Thanks @goulvenclech!
• 9584dc7 Changed sampo update to an optional self-update Cargo feature (enabled by default) so Sampo can be packaged for more package managers that handle updates themselves. Disable it with --no-default-features. — Thanks @nartsisss for your first contribution 🎉!
• Updated dependencies: sampo-core (Cargo)@0.14.1

cargo-sampo-github-bot-v0.4.8

Patch changes

• Updated dependencies: sampo-core (Cargo)@0.14.1

cargo-sampo-github-action-v0.16.1

Patch changes

• 1ee9aa2 Fixed sampo publish creating a spurious git tag and GitHub release for non-publishable, versionless packages (workspace containers and other packages marked as non-publishable without a declared version). Non-publishable but versioned packages are still tagged as before. — Thanks @goulvenclech!
• Updated dependencies: sampo-core (Cargo)@0.14.1

cargo-sampo-core-v0.14.1

Patch changes

• 1ee9aa2 Fixed sampo publish creating a spurious git tag and GitHub release for non-publishable, versionless packages (workspace containers and other packages marked as non-publishable without a declared version). Non-publishable but versioned packages are still tagged as before. — Thanks @goulvenclech!