Skip to content

Conversation

@Greenheart
Copy link
Contributor

This will hopefully resolve #27 and allow the extension to publish a new version.

Fix #27

@cla-bot cla-bot bot added the cla-signed label Jan 6, 2026
Greenheart and others added 2 commits January 6, 2026 18:44
`2024`.

This will hopefully resolve zed-extensions#27 and allow the extension to publish a new
version.
@Stef16Robbe Stef16Robbe merged commit 9f0f99c into zed-extensions:main Jan 6, 2026
5 checks passed
@Stef16Robbe
Copy link
Collaborator

🙏 that this fixes it!

@Greenheart Greenheart deleted the fix/update-zed-extension-api-and-rust-edition branch January 6, 2026 20:10
@Stef16Robbe
Copy link
Collaborator

It did! zed-industries/extensions#4391

So far I've been making releases on Github as well, but it seems that this isn't necessary...

@Greenheart
Copy link
Contributor Author

That's great news! I'll report in the upstream issue too, so hopefully other extensions don't need to run into this problem in the future :)

Yeah, it seems to work even without the releases.

Though, a changelog or releases could be nice to document the major changes for each new extension version. It also makes it easier to know when a certain change was introduced.

Given that we seem to get a Zed bot PR for every release, we might be able to generate changelog entries for all PRs since the latest release by the Zed bot. Not urgent, but could be worth looking into in the future. Though, as long as the extension is super simple like today, it's not as valuable as for a project with several modules and external dependencies where a lot of things could break.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix broken auto publishing for GitHub action

2 participants