GitHub Action for automatically bump Zed Extensions version after a release.
JavaScript
39
22 commits
updated Mar 17, 2026
This action for automatically bump Zed Extensions version after a release.
Create a release.yml file in .github/workflows directory with the following content:
on:
push:
tags:
- "v*"
jobs:
homebrew:
name: Release Zed Extension
runs-on: ubuntu-latest
steps:
- uses: huacnlee/zed-extension-action@v2
with:
extension-name: your-extension-name
push-to: your-name/extensions
env:
# the personal access token should have "repo" & "workflow" scopes
COMMITTER_TOKEN: ${{ secrets.COMMITTER_TOKEN }}
| Name | Description | Required | Default |
|---|---|---|---|
extension-name | The name of your Zed extension. | true | - |
push-to | The forked repository of the zed-industries/extensions repo. | true | - |
tag | Git tag name to use for the extension update | false | Currently pushed tag |
The tag parameter allows you to specify a specific git tag to use for the extension update:
v1.0.0 or refs/tags/v1.0.0When no tag parameter is provided, the action uses the currently pushed tag from the context.
Using a specific tag:
- uses: huacnlee/zed-extension-action@v2
with:
extension-name: your-extension-name
tag: v1.2.3
push-to: your-name/extensions
The COMMITTER_TOKEN is a personal access token with repo and workflow scopes. You can create one in your GitHub settings.
When a new tag is pushed, the action will:
See example: https://github.com/zed-industries/extensions/pull/217
MIT
70 followers · starred Jun 2026
68 followers · starred Jun 2026
143 followers · starred Aug 2025
830 followers · starred Feb 2024
JavaScript
98.4%
TypeScript
1.6%
GitHub Action for automatically bump Zed Extensions version after a release.
JavaScript
39
22 commits
updated Mar 17, 2026
This action for automatically bump Zed Extensions version after a release.
Create a release.yml file in .github/workflows directory with the following content:
on:
push:
tags:
- "v*"
jobs:
homebrew:
name: Release Zed Extension
runs-on: ubuntu-latest
steps:
- uses: huacnlee/zed-extension-action@v2
with:
extension-name: your-extension-name
push-to: your-name/extensions
env:
# the personal access token should have "repo" & "workflow" scopes
COMMITTER_TOKEN: ${{ secrets.COMMITTER_TOKEN }}
| Name | Description | Required | Default |
|---|---|---|---|
extension-name | The name of your Zed extension. | true | - |
push-to | The forked repository of the zed-industries/extensions repo. | true | - |
tag | Git tag name to use for the extension update | false | Currently pushed tag |
The tag parameter allows you to specify a specific git tag to use for the extension update:
v1.0.0 or refs/tags/v1.0.0When no tag parameter is provided, the action uses the currently pushed tag from the context.
Using a specific tag:
- uses: huacnlee/zed-extension-action@v2
with:
extension-name: your-extension-name
tag: v1.2.3
push-to: your-name/extensions
The COMMITTER_TOKEN is a personal access token with repo and workflow scopes. You can create one in your GitHub settings.
When a new tag is pushed, the action will:
See example: https://github.com/zed-industries/extensions/pull/217
MIT
70 followers · starred Jun 2026
68 followers · starred Jun 2026
143 followers · starred Aug 2025
830 followers · starred Feb 2024
JavaScript
98.4%
TypeScript
1.6%