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

[PR #212] [MERGED] ci: persist release tag version to main package.json #1589

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

📋 Pull Request Information

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

Base: main ← Head: codex/issue-209-persist-version-main

📝 Commits (1)

  • 3637f80 ci: persist release version to main

📊 Changes

4 files changed (+44 additions, -1 deletions)

View changed files

📝 .github/workflows/README.md (+1 -0)
📝 .github/workflows/docker-build.yml (+41 -0)
📝 docs/DEVELOPMENT_WORKFLOW.md (+1 -0)
📝 package.json (+1 -1)

📄 Description

Summary

  • add a post-release job in Docker workflow to sync package.json version back to main after v* tag builds
  • keep semver validation on release tags
  • update docs to state the write-back behavior
  • align current package.json version to 3.12.1

Why

The previous change synced version only inside CI build context, so main/package.json stayed stale.

Testing

  • validated workflow YAML parsing locally (ruby -ryaml)
  • inspected diff for tag-path behavior and main write-back logic

Follow-up to #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/212 **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-persist-version-main` --- ### 📝 Commits (1) - [`3637f80`](https://github.com/RayLabsHQ/gitea-mirror/commit/3637f808198293634ab3767fab43fbc3f9f30950) ci: persist release version to main ### 📊 Changes **4 files changed** (+44 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/README.md` (+1 -0) 📝 `.github/workflows/docker-build.yml` (+41 -0) 📝 `docs/DEVELOPMENT_WORKFLOW.md` (+1 -0) 📝 `package.json` (+1 -1) </details> ### 📄 Description ## Summary - add a post-release job in Docker workflow to sync `package.json` version back to `main` after `v*` tag builds - keep semver validation on release tags - update docs to state the write-back behavior - align current `package.json` version to `3.12.1` ## Why The previous change synced version only inside CI build context, so `main/package.json` stayed stale. ## Testing - validated workflow YAML parsing locally (`ruby -ryaml`) - inspected diff for tag-path behavior and main write-back logic Follow-up to #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:45 -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#1589
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?