oblachno-oss/grm
3
0
Fork 0
Code Issues 26 Pull Requests 1 Actions Packages Projects Releases 17 Wiki Activity

GRM-42: Clean up infrastructure-only releases and fix release classification #37

Merged
emil merged 0 commits from GRM-42-fix-releases into master 2026-06-21 21:46:38 +00:00
Conversation 0 Commits - Files Changed -
emil commented 2026-06-21 21:43:48 +00:00
Owner
Copy Link
Copy Source

Problem

Releases v0.2.1 through v0.4.0 were infrastructure-only (release pipeline fixes, documentation, wiki sync, CI refactoring) and should not have been tagged as releases. Updating documentation or workflows must not be part of releases.

Root Causes

  1. only classified as workflow-only, but (configure_repo, check_test_speed, etc.) were also infrastructure — classified as user-facing by default
  2. (version file) was classified as user-facing, so version bumps triggered a circular release loop

What Was Done

Retroactive cleanup (already done):

  • Deleted Gitea releases v0.2.1 through v0.4.0
  • Deleted tags v0.2.1 through v0.4.0 (local + remote)
  • Set back to 0.2.0 (last legitimate release)
  • Cleaned up CHANGELOG.md (removed v0.2.1-v0.4.0 entries)
  • Reverted pyproject.toml to v0.2.0 state (CI config changes were redundant)

Fix (this PR):

  • Changed to in workflow-only patterns (all scripts are infrastructure)
  • Added to workflow-only patterns (version file, not user-facing code)
  • Updated tests to reflect new classification

Verification

After this fix, returns False — all changes since v0.2.0 are correctly classified as workflow-only. The release workflow will skip releases for infrastructure-only changes.

540 tests pass, 100% coverage.

## Problem Releases v0.2.1 through v0.4.0 were infrastructure-only (release pipeline fixes, documentation, wiki sync, CI refactoring) and should not have been tagged as releases. Updating documentation or workflows must not be part of releases. ## Root Causes 1. only classified as workflow-only, but (configure_repo, check_test_speed, etc.) were also infrastructure — classified as user-facing by default 2. (version file) was classified as user-facing, so version bumps triggered a circular release loop ## What Was Done ### Retroactive cleanup (already done): - Deleted Gitea releases v0.2.1 through v0.4.0 - Deleted tags v0.2.1 through v0.4.0 (local + remote) - Set back to 0.2.0 (last legitimate release) - Cleaned up CHANGELOG.md (removed v0.2.1-v0.4.0 entries) - Reverted pyproject.toml to v0.2.0 state (CI config changes were redundant) ### Fix (this PR): - Changed to in workflow-only patterns (all scripts are infrastructure) - Added to workflow-only patterns (version file, not user-facing code) - Updated tests to reflect new classification ## Verification After this fix, returns False — all changes since v0.2.0 are correctly classified as workflow-only. The release workflow will skip releases for infrastructure-only changes. 540 tests pass, 100% coverage.
emil merged commit 516c5b4864 into master 2026-06-21 21:46:38 +00:00
emil deleted branch GRM-42-fix-releases 2026-06-21 21:46:39 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
 ci-improvement
CI workflow improvements
 doc-improvement
Documentation improvements
 feedback
Issues from subagent or agent feedback
 ready-to-merge
Auto-merge PR when all CI checks pass
 refactoring
Large refactoring PR — bypasses size check
 tooling
Tool-related feedback or improvements
 workflow-improvement
Workflow alignment or pattern improvements
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
emil (emil User) emo kireto
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: oblachno-oss/grm#37