Skip to content

test(sync2/F): drop brackets from spaces+parens round-trip case #9

test(sync2/F): drop brackets from spaces+parens round-trip case

test(sync2/F): drop brackets from spaces+parens round-trip case #9

Workflow file for this run

name: Release plugin
on:
push:
tags:
- "[0-9].[0-9]+.[0-9]+*"
jobs:
build:
runs-on: ubuntu-latest
permissions:
contents: write
steps:
- uses: actions/checkout@v3
- name: Use Node.js
uses: actions/setup-node@v3
with:
node-version: "18.x"
- name: Build plugin
run: |
npm install -g pnpm@latest-10
pnpm install
pnpm build
- name: Create release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# Force-push of an already-published tag is a deploy
# scenario we want to support: the tag moves to a newer
# commit, CI re-runs, the artifacts on the release page
# should refresh in place. `gh release create` itself
# errors when a release with the same tag name already
# exists ("a release with the same tag name already
# exists: 2.0.1-beta4" — the 2026-05-25 incident, see
# docs/PSEUDO-MERGE-MODE.md §12.3). Fall through to
# `gh release upload --clobber` to overwrite the per-file
# assets in place when the release already exists.
run: |
if [[ "${{ github.ref_name }}" == *-beta* ]]; then
gh release create "${{ github.ref_name }}" \
--title="${{ github.ref_name }}" \
--prerelease \
main.js manifest.json styles.css \
|| gh release upload "${{ github.ref_name }}" \
main.js manifest.json styles.css --clobber
else
gh release create "${{ github.ref_name }}" \
--title="${{ github.ref_name }}" \
main.js manifest.json styles.css \
|| gh release upload "${{ github.ref_name }}" \
main.js manifest.json styles.css --clobber
fi