RnD/EVOLV
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

Config versioning for backward compatibility #12

New Issue
Open
opened 2026-03-11 13:54:40 +00:00 by vps1_gitea_admin · 0 comments
vps1_gitea_admin commented 2026-03-11 13:54:40 +00:00
Owner
Copy Link

Problem

No versioning on config schemas. If config structure changes, old deployments break silently.

Solution

Add version field to configs with migration functions between versions.

## Problem No versioning on config schemas. If config structure changes, old deployments break silently. ## Solution Add version field to configs with migration functions between versions.
vps1_gitea_admin added the P2-extensibility label 2026-03-11 13:54:40 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-architecture
Must-do structural/design changes for scaling
 P1-cleanup
Quick wins: remove deprecated code, fix inconsistencies
 P2-extensibility
Plugin architecture, output formats, config versioning
 P3-documentation
Docs, wiki, READMEs, architecture diagrams
 P4-testing
Test coverage, CI pipeline, integration tests
 bug
Confirmed bugs
 enhancement
New features / improvements
 security
Credentials, auth, vulnerabilities
 tech-debt
Code quality / cleanup
No Label P2-extensibility
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
vps1_gitea_admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RnD/EVOLV#12
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?