Add release machinery

Author: tnthornton

.github/workflows/ci.yml

@@ -35,7 +35,12 @@ jobs:
     runs-on: ubuntu-24.04
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+        with:
+          submodules: true
+
+      - name: Fetch History
+        run: git fetch --prune --unshallow
 
       - name: Setup Go
         uses: actions/setup-go@v5
@@ -55,7 +60,12 @@ jobs:
     runs-on: ubuntu-24.04
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+        with:
+          submodules: true
+
+      - name: Fetch History
+        run: git fetch --prune --unshallow
 
       - name: Setup Go
         uses: actions/setup-go@v5
@@ -90,7 +100,12 @@ jobs:
           install: true
 
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+        with:
+          submodules: true
+
+      - name: Fetch History
+        run: git fetch --prune --unshallow
 
       # We ask Docker to use GitHub Action's native caching support to speed up
       # the build, per https://docs.docker.com/build/cache/backends/gha/.
@@ -131,7 +146,12 @@ jobs:
       - build
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+        with:
+          submodules: true
+
+      - name: Fetch History
+        run: git fetch --prune --unshallow
 
       - name: Download Single-Platform Packages
         uses: actions/download-artifact@v4

.github/workflows/tag.yaml

@@ -0,0 +1,26 @@
+name: Tag
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Release version (e.g. v0.1.0)'
+        required: true
+      message:
+        description: 'Tag message'
+        required: true
+
+jobs:
+  create-tag:
+    runs-on: blacksmith-2vcpu-ubuntu-2404
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+
+      - name: Create Tag
+        uses: negz/create-tag@39bae1e0932567a58c20dea5a1a0d18358503320 # v1
+        with:
+          version: ${{ github.event.inputs.version }}
+          message: ${{ github.event.inputs.message }}
+          token: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -1,6 +1,7 @@
 # function-openai
 [![CI](https://github.com/upbound/function-openai/actions/workflows/ci.yml/badge.svg)](https://github.com/upbound/function-openai/actions/workflows/ci.yml)
 [![Slack](https://img.shields.io/badge/slack-upbound_crossplane-purple?logo=slack)](https://crossplane.slack.com/archives/C01TRKD4623)
+[![GitHub release](https://img.shields.io/github/release/upbound/function-openai/all.svg)](https://github.com/upbound/function-openai/releases)
 
 Use natural language prompts to compose resources.
 

RELEASE.md

@@ -0,0 +1,26 @@
+## Release Process
+
+This is a slimmed-down version of the release process described [here](https://github.com/crossplane/release).
+
+1. **feature freeze**: Merge all completed features into main development branch
+   of all repos to begin "feature freeze" period.
+1. **branch repo**: Create a new release branch using the GitHub UI for the
+   repo (e.g. `release-0.25`).
+1. **tag release**: Run the `Tag` action on the _release branch_ with the
+   desired version (e.g. `v0.25.0`).
+1. **build/publish**: Run the `CI` action on the tag.
+1. **tag next pre-release**: Run the `tag` action on the main development branch
+   with the `-0.rc.0` for the next release (e.g. `v0.26.0-0.rc.0`). (**NOTE**:
+   we added the `-0.` prefix to allow correctly sorting release candidates)
+1. **verify**: Verify all artifacts have been published successfully, perform
+   sanity testing.
+   - Check in Upbound Marketplace that the new versions are present.
+1. **release notes**:
+   - Open the new release tag in https://github.com/upbound/function-openai/tags and click "Create
+     release from tag".
+   - "Generate release notes" from previous release ("auto" might not work).
+   - Make sure the release notes are complete, presize and well formatted.
+   - Publish the well authored Github release.
+1. **announce**: Announce the release on Twitter, Slack, etc.
+   - Crossplane Slack #Upbound: https://crossplane.slack.com/archives/C01TRKD4623
+   - TODO: where else?