From 73b3fa431cdb09b5e2a8f2d50f8a476a843a6d60 Mon Sep 17 00:00:00 2001 From: rdlabo Date: Thu, 10 Sep 2026 18:31:30 +0900 Subject: [PATCH] fix: publish iOS 26 releases from prefixed tags --- .github/workflows/release.yml | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index e2e4bc6..8b85956 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -3,7 +3,7 @@ name: Release on: push: tags: - - 'v*' + - 'ios26-v*' issue_comment: types: [created] workflow_run: @@ -81,7 +81,7 @@ jobs: id: tag_version run: | TAG_NAME=${GITHUB_REF#refs/tags/} - VERSION=${TAG_NAME#v} + VERSION=${TAG_NAME#ios26-v} echo "version=$VERSION" >> $GITHUB_OUTPUT echo "tag=$TAG_NAME" >> $GITHUB_OUTPUT echo "Extracted version: $VERSION from tag: $TAG_NAME" diff --git a/README.md b/README.md index a1c09a0..877b98f 100644 --- a/README.md +++ b/README.md @@ -224,7 +224,7 @@ When a pull request is merged into `main` or `ios26`, it is automatically publis Candidate code is built in a read-only workflow without npm publishing credentials. The privileged release workflow never checks out or executes pull request code; it revalidates the source workflow and package identity, then publishes only the immutable packed artifact with lifecycle scripts disabled. The install-command comment is a separate best-effort notification and cannot invalidate a successful npm publish. -Only `npm run release` can create a release tag. Stable `vX.Y.Z` tags (major, minor, or patch releases) publish to npm `latest`; revision/prerelease tags publish to `next`. Neither `beta` nor `next` publishing changes the npm `latest` dist-tag. +Only `npm run release` can create a release tag. Stable `ios26-vX.Y.Z` tags (major, minor, or patch releases) publish to npm `latest`; revision/prerelease tags publish to `next`. Neither `beta` nor `next` publishing changes the npm `latest` dist-tag.