feat: import pinned Nextcloud appstore workflow reference - #2
Merged
Merged
Conversation
Signed-off-by: Vitor Mattos <vitor@php.rio>
vitormattos
force-pushed
the
feat/import-nextcloud-appstore-reference
branch
from
September 20, 2026 01:51
cd8a437 to
f16f05f
Compare
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
1 participant
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 immutable upstream reference used to design reusable Nextcloud app release automation.
Source:
nextcloud/.githubcf6248d5ef28a328cde764daf80bc5fae4705adeworkflow-templates/appstore-build-publish.yml4710d78c576abd1c875d799770f67262988119404d58d379656f5932872fcba8The file is deliberately vendored under
upstream/vendor/, not exposed undertemplates/: it remains an upstream design reference, not a LibreCode workflow safe for consumption.Security review identified follow-up design changes before reuse, including checksum verification for downloaded tooling, stronger secret handling, and separation of build/sign/publish privileges.
This PR is stacked on #1; merge #1 first.