Ecosystem Support Tracker

[goulvenclech]

Sampo currently supports the following ecosystems and registries:

Registry	Ecosystem(s)	Versioning	Publishing	Package Manager(s)	Monorepos
Crates	Rust	✅	✅	✅ Cargo	✅
npm	JavaScript/ TypeScript	✅	✅	✅ npm, pnpm, yarn, bun	✅
Hex	Elixir	✅	✅	✅ Mix	✅
	Gleam	⬜	⬜	💡 gleam	✅
	Erlang	⬜	⬜	💡 rebar3	✅
PyPI	Python	✅	✅	✅ uv	✅
Packagist	PHP	✅	✅	✅ Composer	❌

Want to add support for a new ecosystem? Check our Contributing Guidelines and the PackageAdapter implementation in sampo-core to get started. Contributions don't need to be perfect, submit your best effort, and we will gladly assist in polishing the work!

[rafaeelaudibert]

Hey @goulvenclech! I work at PostHog and we're very interested in this project!

We love changesets on our posthog-js JavaScript SDK, and we want the same ease on all of our SDKs. We're still not certain whether sampo is the right solution here, but we might try implementing it!

We might send some contributions your way for the ecosystems we support, and you don't yet - Python is the more important one at the moment, followed by Flutter and iOS.

[goulvenclech]

Hi @rafaeelaudibert ! Thanks a lot for your interest in Sampo 😄

We love changesets on our posthog-js JavaScript SDK, and we want the same ease on all of our SDKs.

I actually started this project to get changesets comfort on my non-TypeScript projects haha great to hear this resonates with what you’re doing at PostHog.

We might send some contributions your way for the ecosystems we support, and you don't yet - Python is the more important one at the moment, followed by Flutter and iOS.

I’m currently on vacation (between two jobs) until mid-January, so I’ll have a good chunk of time to work on Sampo. My first priority is a « quality of life » CLI release with new version hints, an update command, and distributing binaries across OS package registeries.

After that, I’d be happy to tackle Python or Flutter support, depending on what you’ve already started on your side. I’m also very open to contributions, and to filling any gaps you may hit when moving from Changesets to Sampo.

Also, if you’d like a proof of concept, I’m happy to open a PR on one of your repos, with a first draft on how a Sampo-based CI could plug into your workflow.

[rafaeelaudibert]

Hey!

I actually started this project to get changesets comfort on my non-TypeScript projects haha great to hear this resonates with what you’re doing at PostHog.

Oh, that's an awesome blog post, love the intention behind it!

Also, if you’d like a proof of concept, I’m happy to open a PR on one of your repos, with a first draft on how a Sampo-based CI could plug into your workflow.

I might submit an initial PR for Python tomorrow. It'd only cover our use case for now - so pyproject.toml-based and uv as package manager - but it's easy to extend it to other lock + package managers as you have for TS-land.

Once we have that released, we can try it out on posthog-python. We're using GitHub environments, so we will not be interested in using your actions and bot, only on the CLI to automatically convert the changesets into a release and then publish them over to pypi.

[rafaeelaudibert]

Took way longer than "tomorrow", but here it is: #170

PR introducing it to posthog-python is PostHog/posthog-python#398 but there's still a lot missing - updating CI, README, etc.

[rafaeelaudibert]

Hey! This is for PHP: #173

[rafaeelaudibert]

@goulvenclech just to keep you posted, first release on our elixir repo published via sampo!
https://github.com/PostHog/posthog-elixir/actions/runs/21699029858/job/62575622499

Moving PHP, Python and Rust to it tomorrow.