Merges develop into release/0.1 so CI publishes 0.1.0-RC.7 (release/0.1 is at 0.1.0-RC.6).
Brings in:
#40 QQQ 4.1.0-RC.26 / qbit-build-parent 2.2.1 / qqq-frontend-next 1.0.0-RC.38 alignment with the Gitea registry
Upload-job status fix: status is no longer the upload-job table's record-version field (QQQ RC.26 advances version fields on every update, turning status into a UUID); transitions are guarded by re-reading status inside the account-lock transaction
Conflicts resolved: pom keeps revision 0.1.0-RC.6 (CI bumps to RC.7) plus develop's qqq.version; .qqq-ci.yml and .circleci/config.yml taken from develop.
No public API or schema change (the upload-job table drops only its record-version declaration).
Merges develop into release/0.1 so CI publishes **0.1.0-RC.7** (release/0.1 is at 0.1.0-RC.6).
Brings in:
- #40 QQQ 4.1.0-RC.26 / qbit-build-parent 2.2.1 / qqq-frontend-next 1.0.0-RC.38 alignment with the Gitea registry
- Upload-job status fix: `status` is no longer the upload-job table's record-version field (QQQ RC.26 advances version fields on every update, turning status into a UUID); transitions are guarded by re-reading status inside the account-lock transaction
- Shared ci-workflows Gitea build (`.gitea/workflows/build.yaml`), `.qqq-ci.yml` orb 0.8
Conflicts resolved: pom keeps `revision` 0.1.0-RC.6 (CI bumps to RC.7) plus develop's `qqq.version`; `.qqq-ci.yml` and `.circleci/config.yml` taken from develop.
No public API or schema change (the upload-job table drops only its record-version declaration).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Replace the platform-ci release callers with one caller of
KofTwentyTwo/ci-workflows maven.yaml (qqq-orb port).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
QQQ 4.1.0-RC.26 (RecordVersionCheck.advance) advances a table's configured
record-version field on every update; a STRING version becomes a random
UUID. The upload-job table declared status as its version field, so every
update overwrote status with a UUID.
Drop the version field and compare the expected status inside the existing
account-lock transaction, which already serializes transitions across pods.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Merges develop into release/0.1 so CI publishes 0.1.0-RC.7 (release/0.1 is at 0.1.0-RC.6).
Brings in:
statusis no longer the upload-job table's record-version field (QQQ RC.26 advances version fields on every update, turning status into a UUID); transitions are guarded by re-reading status inside the account-lock transaction.gitea/workflows/build.yaml),.qqq-ci.ymlorb 0.8Conflicts resolved: pom keeps
revision0.1.0-RC.6 (CI bumps to RC.7) plus develop'sqqq.version;.qqq-ci.ymland.circleci/config.ymltaken from develop.No public API or schema change (the upload-job table drops only its record-version declaration).
🤖 Generated with Claude Code