Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Document release/version process SOP #68

New Issue
Open
opened 2026-07-02 05:43:27 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:43:27 -05:00
Owner
Copy Link
Copy Source

The repo has release/version tooling, but the standard release process is not clearly documented. Add a release SOP covering version bumping, changelog/release notes, testing, merge, tagging, and cleanup.

Related existing work: #48 (issue-linked branches + release tagging standard), #50 (release-tag automation helper), #51 (closed-not-merged reconciliation), #63 (Release v1.1.0). This issue is the documentation SOP that ties those together; not a duplicate.

Acceptance criteria

  • Documents whether the repo is master-based or uses a dev/release branch.
  • Documents how to decide patch/minor/major version bumps.
  • Documents how to prepare a version bump PR.
  • Documents required checks before release.
  • Documents how and when to run scripts/release-tag.
  • Documents who is allowed to merge/tag.
  • Documents branch/worktree cleanup after release.
  • Clarifies that self-review/self-merge rules still apply.
The repo has release/version tooling, but the standard release process is not clearly documented. Add a release SOP covering version bumping, changelog/release notes, testing, merge, tagging, and cleanup. Related existing work: #48 (issue-linked branches + release tagging standard), #50 (release-tag automation helper), #51 (closed-not-merged reconciliation), #63 (Release v1.1.0). This issue is the documentation SOP that ties those together; not a duplicate. ## Acceptance criteria * Documents whether the repo is master-based or uses a dev/release branch. * Documents how to decide patch/minor/major version bumps. * Documents how to prepare a version bump PR. * Documents required checks before release. * Documents how and when to run `scripts/release-tag`. * Documents who is allowed to merge/tag. * Documents branch/worktree cleanup after release. * Clarifies that self-review/self-merge rules still apply.
jcwalker3 added the documentationrelease labels 2026-07-02 05:44:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label documentation release
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#68
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?