mirror of
https://github.com/priyanshujain/sanderling.git
synced 2026-10-02 19:17:10 +00:00
pj
83015d89f0
minor or major, nothing else. A manual patch would republish an identical commit under the next patch number, and a version typed by hand is the one way to get a release that does not follow from the tag before it. Claude-Session: https://claude.ai/code/session_01ShuAy8q8ZfPi8KHxwc8JpQ
41 lines
1.3 KiB
YAML
41 lines
1.3 KiB
YAML
name: release
|
|
|
|
# Promotes the last release to a milestone. ci cuts a patch on every merge, so
|
|
# the released versions run 0.1.4, 0.1.5, 0.1.6; this marks the one you have
|
|
# been running as 0.2.0 and publishes it under that name. The release notes
|
|
# reach back over every patch being consolidated.
|
|
#
|
|
# It runs no checks of its own and needs none. The commit it releases is the one
|
|
# the last release was cut from, and that commit only carries a tag because a
|
|
# whole ci run went green on it.
|
|
#
|
|
# There is no box to type a version into. The two entries below are the only two
|
|
# things a promotion can mean, and a version named by hand is the one way to get
|
|
# a release that does not follow from the tag before it.
|
|
on:
|
|
workflow_dispatch:
|
|
inputs:
|
|
bump:
|
|
description: Consolidate the patches since the last release at this level
|
|
type: choice
|
|
options:
|
|
- minor
|
|
- major
|
|
default: minor
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
release:
|
|
name: Release
|
|
# No sha: this releases the commit the last release was cut from rather than
|
|
# whatever master has drifted to since.
|
|
uses: ./.github/workflows/release-publish.yml
|
|
permissions:
|
|
contents: write
|
|
with:
|
|
bump: ${{ inputs.bump }}
|
|
secrets:
|
|
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
|