(Runtime) Publish Prereleases Manual #40
Workflow file for this run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: (Runtime) Publish Prereleases Manual | ||
on: | ||
workflow_dispatch: | ||
inputs: | ||
prerelease_commit_sha: | ||
required: true | ||
permissions: {} | ||
env: | ||
TZ: /usr/share/zoneinfo/America/Los_Angeles | ||
jobs: | ||
publish_prerelease_canary: | ||
name: Publish to Canary channel | ||
uses: facebook/react/.github/workflows/runtime_prereleases.yml@main | ||
permissions: | ||
# We use github.token to download the build artifact from a previous runtime_build_and_test.yml run | ||
actions: read | ||
with: | ||
commit_sha: ${{ inputs.prerelease_commit_sha }} | ||
release_channel: stable | ||
# The tags to use when publishing canaries. The main one we should | ||
# always include is "canary" but we can use multiple (e.g. alpha, | ||
# beta, rc). To declare multiple, use a comma-separated string, like | ||
# this: | ||
# dist_tag: "canary,alpha,beta,rc" | ||
# | ||
# TODO: We currently tag canaries with "next" in addition to "canary" | ||
# because this used to be called the "next" channel and some | ||
# downstream consumers might still expect that tag. We can remove this | ||
# after some time has elapsed and the change has been communicated. | ||
dist_tag: canary,next | ||
secrets: | ||
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
Check failure on line 38 in .github/workflows/runtime_prereleases_manual.yml
|
||
publish_prerelease_experimental: | ||
name: Publish to Experimental channel | ||
uses: facebook/react/.github/workflows/runtime_prereleases.yml@main | ||
permissions: | ||
# We use github.token to download the build artifact from a previous runtime_build_and_test.yml run | ||
actions: read | ||
# NOTE: Intentionally running these jobs sequentially because npm | ||
# will sometimes fail if you try to concurrently publish two | ||
# different versions of the same package, even if they use different | ||
# dist tags. | ||
needs: publish_prerelease_canary | ||
with: | ||
commit_sha: ${{ inputs.prerelease_commit_sha }} | ||
release_channel: experimental | ||
dist_tag: experimental | ||
secrets: | ||
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} |