File tree Expand file tree Collapse file tree 2 files changed +52
-0
lines changed
Expand file tree Collapse file tree 2 files changed +52
-0
lines changed Original file line number Diff line number Diff line change 1+ name : Tag
2+
3+ on :
4+ workflow_dispatch :
5+ inputs :
6+ version :
7+ description : ' Release version (e.g. v0.1.0)'
8+ required : true
9+ message :
10+ description : ' Tag message'
11+ required : true
12+
13+ jobs :
14+ create-tag :
15+ runs-on : blacksmith-2vcpu-ubuntu-2404
16+
17+ steps :
18+ - name : Checkout
19+ uses : actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
20+
21+ - name : Create Tag
22+ uses : negz/create-tag@39bae1e0932567a58c20dea5a1a0d18358503320 # v1
23+ with :
24+ version : ${{ github.event.inputs.version }}
25+ message : ${{ github.event.inputs.message }}
26+ token : ${{ secrets.GITHUB_TOKEN }}
Original file line number Diff line number Diff line change 1+ ## Release Process
2+
3+ This is a slimmed-down version of the release process described [ here] ( https://github.com/crossplane/release ) .
4+
5+ 1 . ** feature freeze** : Merge all completed features into main development branch
6+ of all repos to begin "feature freeze" period.
7+ 1 . ** branch repo** : Create a new release branch using the GitHub UI for the
8+ repo (e.g. ` release-0.25 ` ).
9+ 1 . ** tag release** : Run the ` Tag ` action on the _ release branch_ with the
10+ desired version (e.g. ` v0.25.0 ` ).
11+ 1 . ** build/publish** : Run the ` CI ` action on the tag.
12+ 1 . ** tag next pre-release** : Run the ` tag ` action on the main development branch
13+ with the ` -0.rc.0 ` for the next release (e.g. ` v0.26.0-0.rc.0 ` ). (** NOTE** :
14+ we added the ` -0. ` prefix to allow correctly sorting release candidates)
15+ 1 . ** verify** : Verify all artifacts have been published successfully, perform
16+ sanity testing.
17+ - Check in Upbound Marketplace that the new versions are present.
18+ 1 . ** release notes** :
19+ - Open the new release tag in https://github.com/upbound/marketplace-mcp-server/tags and click "Create
20+ release from tag".
21+ - "Generate release notes" from previous release ("auto" might not work).
22+ - Make sure the release notes are complete, presize and well formatted.
23+ - Publish the well authored Github release.
24+ 1 . ** announce** : Announce the release on Twitter, Slack, etc.
25+ - Crossplane Slack #Upbound: https://crossplane.slack.com/archives/C01TRKD4623
26+ - TODO: where else?
You can’t perform that action at this time.
0 commit comments