GovOPlaN/govoplan
1
0
Fork 0
Code Issues 10 Pull Requests Actions 3 Packages Projects Releases Wiki Activity

[Feature] Make the Release Console guided, resumable, and repository-aware #15

New Issue
Open
opened 2026-07-22 03:46:14 +02:00 by zemion · 3 comments
zemion commented 2026-07-22 03:46:14 +02:00
Owner
Copy Link

Goal

Turn the Release Console into a versatile, guided operator workflow that supports Core and the different module repository shapes without exposing invalid or unsafe actions.

This is a focused implementation follow-up to #13. Guarded Core source tagging and publication from commit 30f9ed1 are the first integrated foundation.

Acceptance Criteria

  • Model release work as an explicit, resumable sequence: doctor/preflight, target selection, version/contract/migration gates, tag, build/sign/package, publish, catalog update, source publication, and install verification.
  • Derive available steps from repository capabilities so Core, backend-only modules, WebUI modules, documentation, and catalog artifacts receive the right workflow.
  • Show the recommended next action, prerequisites, blocking reasons, and remediation; keep unavailable actions visible but disabled.
  • Provide a complete preview/dry run before mutation and require narrowly scoped confirmations for tag, publish, signing, and catalog changes.
  • Support dependency-ordered multi-repository plans, partial-failure reporting, safe retries, and continuation from durable run state.
  • Distinguish local source state, remote tags, package publication, catalog publication, and installed release state.
  • Record privacy-safe audit events for every mutating step without exposing credentials, signing material, or bearer tokens.
  • Exercise Core and representative module release paths, stale/dirty worktrees, alignment failures, signing failures, publication retries, and interrupted-run recovery in automated tests.

UX Direction

Use the shared Card, DataGrid, status, confirmation, and top-right Save/Discard/action patterns. The console should explain why a step is blocked and guide the operator to the next safe step rather than presenting a flat set of release buttons.

## Goal Turn the Release Console into a versatile, guided operator workflow that supports Core and the different module repository shapes without exposing invalid or unsafe actions. This is a focused implementation follow-up to #13. Guarded Core source tagging and publication from commit `30f9ed1` are the first integrated foundation. ## Acceptance Criteria - [ ] Model release work as an explicit, resumable sequence: doctor/preflight, target selection, version/contract/migration gates, tag, build/sign/package, publish, catalog update, source publication, and install verification. - [ ] Derive available steps from repository capabilities so Core, backend-only modules, WebUI modules, documentation, and catalog artifacts receive the right workflow. - [ ] Show the recommended next action, prerequisites, blocking reasons, and remediation; keep unavailable actions visible but disabled. - [ ] Provide a complete preview/dry run before mutation and require narrowly scoped confirmations for tag, publish, signing, and catalog changes. - [ ] Support dependency-ordered multi-repository plans, partial-failure reporting, safe retries, and continuation from durable run state. - [ ] Distinguish local source state, remote tags, package publication, catalog publication, and installed release state. - [ ] Record privacy-safe audit events for every mutating step without exposing credentials, signing material, or bearer tokens. - [ ] Exercise Core and representative module release paths, stale/dirty worktrees, alignment failures, signing failures, publication retries, and interrupted-run recovery in automated tests. ## UX Direction Use the shared Card, DataGrid, status, confirmation, and top-right Save/Discard/action patterns. The console should explain *why* a step is blocked and guide the operator to the next safe step rather than presenting a flat set of release buttons.
zemion commented 2026-07-22 10:49:59 +02:00
Author
Owner
Copy Link

Progress 2026-07-22: the release workflow now blocks selected WebUI module/version drift at planning, tag mutation, and signed-catalog generation (5447299), including a no-partial-tag regression. A real release exercise published exact annotated tags for Core v0.1.13 and Campaign v0.1.10, built both remote Git references, validated full pip dependency resolution, signed stable catalog sequence 202607220843 with release-key-1, and atomically published website tag catalog-stable-202607220843. Core v0.1.13 also repairs wheel-only Alembic runtime packaging and locks Campaign 0.1.10. Remaining #15 scope includes durable/resumable run state and a first-class deployed/public-catalog state; the production nginx endpoint currently needs an operator rebuild after the catalog repository push.

Progress 2026-07-22: the release workflow now blocks selected WebUI module/version drift at planning, tag mutation, and signed-catalog generation (`5447299`), including a no-partial-tag regression. A real release exercise published exact annotated tags for Core v0.1.13 and Campaign v0.1.10, built both remote Git references, validated full pip dependency resolution, signed stable catalog sequence 202607220843 with `release-key-1`, and atomically published website tag `catalog-stable-202607220843`. Core v0.1.13 also repairs wheel-only Alembic runtime packaging and locks Campaign 0.1.10. Remaining #15 scope includes durable/resumable run state and a first-class deployed/public-catalog state; the production nginx endpoint currently needs an operator rebuild after the catalog repository push.
zemion commented 2026-07-22 15:39:01 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • The mandatory release-composition gate exposed and rejected a stale Campaign backend pin.
  • Aligned requirements-release.txt to Campaign v0.1.10, matching Core's bundled Campaign WebUI and the signed stable catalog.

Changed Files

  • requirements-release.txt

Verification

  • Version alignment passed for all 65 repositories including the release composition; 23 release/version tests passed.

Next / Blocked

  • The larger guided, resumable, repository-aware Release Console work remains open.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - The mandatory release-composition gate exposed and rejected a stale Campaign backend pin. - Aligned requirements-release.txt to Campaign v0.1.10, matching Core's bundled Campaign WebUI and the signed stable catalog. ### Changed Files - `requirements-release.txt` ### Verification - `Version alignment passed for all 65 repositories including the release composition; 23 release/version tests passed.` ### Next / Blocked - The larger guided, resumable, repository-aware Release Console work remains open. Suggested status label: `status/in-progress`
zemion commented 2026-07-22 17:19:16 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Selective plans now expose structured gate findings, a recommended next action, remediation, and source-preflight readiness.
  • Malformed repository, Core WebUI bundle, Core dashboard, and manifest metadata now fail closed as blocked plans instead of becoming HTTP 500 errors.
  • A real Core 0.1.13 plan reaches tag preview; Files 0.1.9 is correctly blocked with exact Core release bundle and lockfile remediation.

Changed Files

  • tools/release/govoplan_release/selective_planner.py
  • tools/release/govoplan_release/dashboard.py
  • tools/release/webui/index.html

Verification

  • 103 meta tests passed; version alignment passed for 65 repositories; static contracts passed

Next / Blocked

  • Durable resumable run state, dependency-ordered execution, audited mutations, safe retries, and interrupted-run recovery remain open.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Selective plans now expose structured gate findings, a recommended next action, remediation, and source-preflight readiness. - Malformed repository, Core WebUI bundle, Core dashboard, and manifest metadata now fail closed as blocked plans instead of becoming HTTP 500 errors. - A real Core 0.1.13 plan reaches tag preview; Files 0.1.9 is correctly blocked with exact Core release bundle and lockfile remediation. ### Changed Files - `tools/release/govoplan_release/selective_planner.py` - `tools/release/govoplan_release/dashboard.py` - `tools/release/webui/index.html` ### Verification - `103 meta tests passed; version alignment passed for 65 repositories; static contracts passed` ### Next / Blocked - Durable resumable run state, dependency-ordered execution, audited mutations, safe retries, and interrupted-run recovery remain open. Suggested status label: `status/in-progress`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dataflow
GovOPlaN Dataflow module behavior or integration.
module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#15
No description provided.
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?