github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-08 05:18:55 -05:00
Code Issues 103 Packages Projects Releases 93 Wiki Activity

[PR #211] [MERGED] ci: automate release version bump in CI #1588

New Issue
Closed
opened 2026-04-24 18:20:42 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-24 18:20:42 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/211
Author: @arunavo4
Created: 3/5/2026
Status: ✅ Merged
Merged: 3/5/2026
Merged by: @arunavo4

Base: main ← Head: codex/issue-209-release-version-ci

📝 Commits (1)

  • 66f397e ci: automate release version from tag

📊 Changes

3 files changed (+32 additions, -11 deletions)

View changed files

📝 .github/workflows/README.md (+2 -0)
📝 .github/workflows/docker-build.yml (+23 -2)
📝 docs/DEVELOPMENT_WORKFLOW.md (+7 -9)

📄 Description

Summary

  • auto-derive release version from v* tags in Docker release workflow
  • validate tag format as semver before build (vX.Y.Z, optional prerelease/build)
  • sync package.json version in CI build context from the release tag so runtime version is correct in release images
  • update workflow and release-process docs

Why

Manual version bumping was easy to forget during releases.

Testing

  • validated workflow YAML parses successfully
  • reviewed workflow diff for tag and non-tag paths

Closes #209

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/211 **Author:** [@arunavo4](https://github.com/arunavo4) **Created:** 3/5/2026 **Status:** ✅ Merged **Merged:** 3/5/2026 **Merged by:** [@arunavo4](https://github.com/arunavo4) **Base:** `main` ← **Head:** `codex/issue-209-release-version-ci` --- ### 📝 Commits (1) - [`66f397e`](https://github.com/RayLabsHQ/gitea-mirror/commit/66f397e251150383c09b521e8b056520049c8eea) ci: automate release version from tag ### 📊 Changes **3 files changed** (+32 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/README.md` (+2 -0) 📝 `.github/workflows/docker-build.yml` (+23 -2) 📝 `docs/DEVELOPMENT_WORKFLOW.md` (+7 -9) </details> ### 📄 Description ## Summary - auto-derive release version from `v*` tags in Docker release workflow - validate tag format as semver before build (`vX.Y.Z`, optional prerelease/build) - sync `package.json` version in CI build context from the release tag so runtime version is correct in release images - update workflow and release-process docs ## Why Manual version bumping was easy to forget during releases. ## Testing - validated workflow YAML parses successfully - reviewed workflow diff for tag and non-tag paths Closes #209 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-24 18:20:42 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#1588
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?