feat: add reusable Nextcloud release plan - #3
Merged
Merged
Conversation
Signed-off-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: Vitor Mattos <vitor@php.rio>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add the first non-mutating reusable workflow for Nextcloud app releases.
The planner validates:
appinfo/info.xmlversion;Architecture
The reusable workflow is limited to workflow-level orchestration: permissions, runner selection and checkouts.
Release planning is encapsulated by the
actions/release-plancomposite action. The action maps declared inputs to a small environment contract and invokes the tested Python planner. Parsing, release rules, GitHub checks, exit status and step-summary rendering remain in Python instead of inline workflow shell.This keeps the shared workflow declarative while following GitHub's documented separation between reusable workflows and composite actions.
The release policy remains caller-owned: the shared workflow does not hard-code LibreSign labels or repository conventions.
This is the first implementation step for LibreCodeCoop/github-governance#5. Signing, artifact publication and App Store credentials remain outside the planning stage.