Files
zeekay faa9bd13a9 move the release build here; publish to run artifacts, not a GitHub release
The build and the two zips are unchanged. What changed is where the workflow
lives — the forge collects the first WORKFLOW_DIRS entry that exists, so
.github/workflows is the side that goes quiet — the runner label, since
nothing here advertises ubuntu-latest and an unmatched label queues instead of
failing, and the final step: softprops/action-gh-release posts to
api.github.com. The zips are uploaded as run artifacts now, so a tag still
produces retrievable Chrome and Firefox packages, but there is no public
download page for them.

docs.yml is dropped outright: actions/deploy-pages publishes to GitHub Pages,
which this forge does not host.
2026-08-13 21:08:04 -07:00

54 lines
1.4 KiB
YAML

name: Release
on:
push:
tags:
- 'v*'
permissions:
contents: write
jobs:
build:
runs-on: hanzo-build-linux-amd64
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci || npm install
- name: Build extension
run: npm run build
- name: Get version
id: version
run: echo "version=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
- name: Package Chrome extension
run: |
cd dist/browser-extension/chrome
zip -r ../../../hanzo-ai-chrome-${{ steps.version.outputs.version }}.zip .
- name: Package Firefox extension
run: |
cd dist/browser-extension/firefox
zip -r ../../../hanzo-ai-firefox-${{ steps.version.outputs.version }}.zip .
# softprops/action-gh-release used to attach these zips to a GitHub
# release. It talks to api.github.com, which is not this forge, so the
# packages are kept as run artifacts instead — retrievable from the run,
# not from a public download page.
- uses: actions/upload-artifact@v4
with:
name: hanzo-ai-extension-${{ steps.version.outputs.version }}
path: |
hanzo-ai-chrome-*.zip
hanzo-ai-firefox-*.zip
retention-days: 30