Merge the existing release/0.1 ancestry into develop, retaining current develop CI configuration and the 0.1.0-SNAPSHOT revision. Old release-line changes were only historical CI configuration and the previous RC POM revision. The resulting tree differs from current develop ONLY by a CHANGELOG entry; application code, schema, dependencies and the canonical Gitea caller remain byte-identical. Both parents are preserved so the next normal cut into release/0.1 is conflict-free. No manual publication, version selection, tag, gate bypass or release lock cleanup is included.
Merge the existing release/0.1 ancestry into develop, retaining current develop CI configuration and the 0.1.0-SNAPSHOT revision. Old release-line changes were only historical CI configuration and the previous RC POM revision. The resulting tree differs from current develop ONLY by a CHANGELOG entry; application code, schema, dependencies and the canonical Gitea caller remain byte-identical. Both parents are preserved so the next normal cut into release/0.1 is conflict-free. No manual publication, version selection, tag, gate bypass or release lock cleanup is included.
Preserve current develop CI configuration and SNAPSHOT revision; application source is unchanged. Reconcile the prior release ancestry so normal Gitea RC cuts can merge without obsolete CI conflicts.
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Codex <noreply@openai.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.
Merge the existing release/0.1 ancestry into develop, retaining current develop CI configuration and the 0.1.0-SNAPSHOT revision. Old release-line changes were only historical CI configuration and the previous RC POM revision. The resulting tree differs from current develop ONLY by a CHANGELOG entry; application code, schema, dependencies and the canonical Gitea caller remain byte-identical. Both parents are preserved so the next normal cut into release/0.1 is conflict-free. No manual publication, version selection, tag, gate bypass or release lock cleanup is included.