bots-garden/mini-me-kit · 1982516

modified .github/workflows/release.yml +13 -4 Viewed

@@ -1,9 +1,8 @@
1	1	name: Release
2	2
3		-# Publishes a release with the cross-compiled binaries whenever a tag v* is
4		-# pushed — what ./01-release.tag.sh does at its last line. The binaries are
5		-# built by ./02-build-releases.sh, the same script one runs on a laptop, so a
6		-# local build and a published one are byte-for-byte the same pipeline.
	3	+# Publishes a release whenever a tag v* is pushed — what ./01-release.tag.sh
	4	+# does at its last line. Nothing is built: this repository ships no binaries,
	5	+# the release only marks the tagged commit and carries the tag's message.
7	6	#
8	7	# Rickub runs this as an ordinary GitHub Actions workflow. Two platform facts
9	8	# matter here: the job's GITHUB_TOKEN is the ONLY credential the release API
@@ -36,6 +35,16 @@ jobs:
36	35	# from the annotated tag's message.
37	36	fetch-depth: 0
38	37
	38	+ # actions/checkout can leave a lightweight copy of the tag behind, which
	39	+ # has no message; fetching it again restores the annotated tag.
	40	+ - name: Release notes from the tag message
	41	+ id: notes
	42	+ run: \|
	43	+ git fetch --force origin "refs/tags/${GITHUB_REF_NAME}:refs/tags/${GITHUB_REF_NAME}"
	44	+ path="${RUNNER_TEMP}/notes.md"
	45	+ git tag -l --format='%(contents)' "${GITHUB_REF_NAME}" > "${path}"
	46	+ echo "path=${path}" >> "${GITHUB_OUTPUT}"
	47	+
39	48	- name: Publish the release
40	49	uses: softprops/action-gh-release@v2
41	50	with:

  name: Release
--# Publishes a release with the cross-compiled binaries whenever a tag v* is
++# Publishes a release whenever a tag v* is pushed — what ./01-release.tag.sh
--# pushed — what ./01-release.tag.sh does at its last line. The binaries are
++# does at its last line. Nothing is built: this repository ships no binaries,
--# built by ./02-build-releases.sh, the same script one runs on a laptop, so a
++# the release only marks the tagged commit and carries the tag's message.
--# local build and a published one are byte-for-byte the same pipeline.
  #
  # Rickub runs this as an ordinary GitHub Actions workflow. Two platform facts
  # matter here: the job's GITHUB_TOKEN is the ONLY credential the release API
            # from the annotated tag's message.
            fetch-depth: 0
++      # actions/checkout can leave a lightweight copy of the tag behind, which
++      # has no message; fetching it again restores the annotated tag.
++      - name: Release notes from the tag message
++        id: notes
++        run: |
++          git fetch --force origin "refs/tags/${GITHUB_REF_NAME}:refs/tags/${GITHUB_REF_NAME}"
++          path="${RUNNER_TEMP}/notes.md"
++          git tag -l --format='%(contents)' "${GITHUB_REF_NAME}" > "${path}"
++          echo "path=${path}" >> "${GITHUB_OUTPUT}"
++
        - name: Publish the release
          uses: softprops/action-gh-release@v2
          with:

modified 01-release.tag.sh +2 -2 Viewed

@@ -3,8 +3,8 @@
3	3	1. Update TAG and ABOUT in release.env
4	4	2. Run this script: ./01-release.tag.sh (commit, push, tag, push the tag)
5	5	3. Watch the "Release" workflow on Rickub (Actions tab): the tag push starts
6		- it; it builds the binaries with ./02-build-releases.sh and publishes the
7		- release with them, using the job's own token. No personal token is needed.
	6	+ it and publishes the release (no binaries, the tag message as notes),
	7	+ using the job's own token. No personal token is needed.
8	8	COMMENT
9	9
10	10	# Without this, a failing step is ignored and the next one runs anyway. That is

 . Update TAG and ABOUT in release.env
 . Run this script: ./01-release.tag.sh   (commit, push, tag, push the tag)
 . Watch the "Release" workflow on Rickub (Actions tab): the tag push starts
--   it; it builds the binaries with ./02-build-releases.sh and publishes the
++   it and publishes the release (no binaries, the tag message as notes),
--   release with them, using the job's own token. No personal token is needed.
++   using the job's own token. No personal token is needed.
  COMMENT
  # Without this, a failing step is ignored and the next one runs anyway. That is

modified release.env +1 -1 Viewed

@@ -1,5 +1,5 @@
1	1	# ./01-release.tag.sh commit, tag, push
2		-TAG="v0.0.0"
	2	+TAG="v0.0.1"
3	3	ABOUT="Mini Me"
4	4	OWNER="bots-garden"
5	5	REPO="mini-me-kit"

  #   ./01-release.tag.sh              commit, tag, push
--TAG="v0.0.0"
++TAG="v0.0.1"
  ABOUT="Mini Me"
  OWNER="bots-garden"
  REPO="mini-me-kit"

📦 Mini MeUnverified