Public Access
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
# DEVX-156: Fix commit message format and release new CI modules
|
|
|
|
## Problem
|
|
The DEVX-155 merge commit on master has an invalid format
|
|
('DEVX-155: Replace...' missing conventional commit type). This blocks
|
|
the post-merge release workflow's `validate_commit_msg` step, preventing
|
|
`validate_spec`, `check_pr_size`, `nightly_gate`, and `create_dependency_pr`
|
|
from being published to the Gitea PyPI registry. All downstream repos
|
|
(grm, infra, sso-bridge) are blocked — their CI fails with
|
|
`No module named devx.ci.validate_spec`.
|
|
|
|
## Approach
|
|
Add a trivial user-facing change (version doc comment) with a proper
|
|
conventional commit format to trigger the post-merge release workflow.
|
|
The release will publish the new CI modules that DEVX-155 introduced.
|
|
|
|
REQ-1: Add a user-facing change to src/devx/ to trigger release
|
|
REQ-2: Ensure the commit message follows conventional format (type: description)
|
|
|
|
## Test Plan
|
|
- Verify post-merge workflow runs successfully after merge
|
|
- Verify a new release tag is created (v0.51.0 or similar)
|
|
- Verify devx.ci.validate_spec is importable from the published package
|
|
|
|
## Deploy Plan
|
|
- Merge to master via auto-merge workflow
|
|
- Post-merge workflow auto-releases and publishes
|
|
|
|
## Rollback Plan
|
|
- Revert the merge commit if release fails
|
|
|
|
## Acceptance Criteria
|
|
- [x] REQ-1: A user-facing change is added to src/devx/
|
|
- [x] REQ-2: Commit message follows conventional format
|