2025-11-13 - 2026-11-13
Overview
4 Releases published by 2 users
Published
v0.2.0-RC.1
Published
v0.1.0-RC.2
Published
v0.1.0-RC.1
Published
publish-session-20261021-b5276ab
18 Pull requests merged by 2 users
Merged
#26 build(deps): align with Gitea registry (parent 2.2.1, QQQ 4.1.0-RC.26)
Merged
#25 Release 0.1: session-id hashing and PostgreSQL schema for the next RC
Merged
#24 Session store: hash session ids into storage keys; publish the PostgreSQL schema (KOF22 integration)
Merged
#23 build(release): prepare the first published release (0.1.0) on core 4.1.0-RC.22
Merged
#22 ci: pin shared workflow to v1
Merged
#21 ci: use shared ci-workflows Maven workflow
Merged
#19 ci: add the QRun release caller
Merged
#20 ci: enroll shared Gitea release-candidate lifecycle
Merged
#16 ci: adopt managed orb 0.8 patch track
Merged
#15 ci: adopt central orb 0.7.12 and stable gates
Merged
#14 ci: centralize RC release completion in qqq orb
Merged
#13 ci: publish GA artifacts only from stable tags
Merged
#12 ci: adopt shared orb 0.7.11
Merged
#11 ci: adopt shared QQQ orb standard
Merged
#8 ci(release-rc): pass secrets so the shared workflow can sign the RC tag
Merged
#10 build: move to released QQQ 4.1.0-RC.18
Merged
#4 ci: automate RC releases; hotfix/* pushes no longer publish
Merged
#3 ci: publish only GA tags (vX.Y.Z), never RC tags
3 Pull requests proposed by 1 user
Proposed
#1 chore(deps-dev): bump org.assertj:assertj-core from 3.27.3 to 3.27.7 in the maven group across 1 directory
Proposed
#17 WIP: fix: patch AssertJ in the coordinated session-store candidate
Proposed
#18 WIP: test: verify shared sessions after Redis promotion
1 Issue closed from 1 user
Closed
#9 develop build red: qqq-bom-pom 0.40.0-SNAPSHOT no longer resolves
3 Issues created by 1 user
Opened
#5 Build broken: imports expired com.kingsrook.qqq:qqq-bom-pom:0.40.0-SNAPSHOT
Opened
#7 develop fails to build: qqq-bom-pom 0.40.0-SNAPSHOT import no longer resolves
Opened
#9 develop build red: qqq-bom-pom 0.40.0-SNAPSHOT no longer resolves