You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a4bcf23 To avoid ambiguity between packages in different ecosystems (e.g. a Rust crate and an npm package both named example), Sampo now assigns canonical identifiers to all packages using <ecosystem>/<name>, such as cargo/example for Rust crates or npm/example for JavaScript packages.
Changesets, the CLI, and the GitHub Action now accept and emit ecosystem-qualified package names. Plain package names (without ecosystem prefix) are still supported when there is no ambiguity. — Thanks @goulvenclech!
Patch changes
99b5683 Each sampo and sampo-github-action GitHub release should now include binaries with proper names and formats. — Thanks @goulvenclech!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Minor changes
a4bcf23 To avoid ambiguity between packages in different ecosystems (e.g. a Rust crate and an npm package both named
example), Sampo now assigns canonical identifiers to all packages using<ecosystem>/<name>, such ascargo/examplefor Rust crates ornpm/examplefor JavaScript packages.Changesets, the CLI, and the GitHub Action now accept and emit ecosystem-qualified package names. Plain package names (without ecosystem prefix) are still supported when there is no ambiguity. — Thanks @goulvenclech!
Patch changes
sampoandsampo-github-actionGitHub release should now include binaries with proper names and formats. — Thanks @goulvenclech!—
See release page: https://github.com/bruits/sampo/releases/tag/sampo-v0.10.0
Beta Was this translation helpful? Give feedback.
All reactions