Skip to content

docs: explain reusable release tooling for other Nextcloud apps #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vitormattos merged 1 commit into from
Oct 3, 2026
Merged

docs: explain reusable release tooling for other Nextcloud apps #102

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions developer_manual/release-process.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@ There are only two semantic human release gates: merging the generated release P
.. toctree::
:maxdepth: 2

release-process/reusable-tooling
release-process/configuration
release-process/preparing
release-process/versioning
Expand Down
46 changes: 46 additions & 0 deletions developer_manual/release-process/reusable-tooling.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
.. SPDX-FileCopyrightText: 2026 LibreCode coop and contributors
.. SPDX-License-Identifier: AGPL-3.0-or-later

Reusable release tooling
========================

LibreSign is the reference consumer of LibreCode's reusable release tooling.
The reusable pieces are intentionally independent of LibreSign application
code.

``LibreCodeCoop/release-tool``
Owns release policy, contracts, the PHP/PHAR runtime, release planning,
changelog/version transitions, draft creation, publication verification and
the public lifecycle Actions.

``LibreCodeCoop/.github``
Owns the organization workflow catalog, managed workflow distribution,
synchronization helpers and organization-level automation.

``LibreSign/libresign``
Supplies the consumer configuration, stable branches, changelog/version
files, repository-specific packaging rules and publisher workflow.

The former ``LibreCodeCoop/github-workflows`` repository is retired and should
not be used by new consumers.

Adopting the tooling in another app
-----------------------------------

Start with the generic guides maintained next to Release Tool:

* `Getting started <https://github.com/LibreCodeCoop/release-tool/blob/main/docs/getting-started.md>`_
* `Consumer configuration <https://github.com/LibreCodeCoop/release-tool/blob/main/docs/consumer-configuration.md>`_
* `Release lifecycle <https://github.com/LibreCodeCoop/release-tool/blob/main/docs/release-lifecycle.md>`_
* `GitHub Actions integration <https://github.com/LibreCodeCoop/release-tool/blob/main/docs/github-actions.md>`_
* `GitHub App setup <https://github.com/LibreCodeCoop/release-tool/blob/main/docs/github-app.md>`_
* `Troubleshooting <https://github.com/LibreCodeCoop/release-tool/blob/main/docs/troubleshooting.md>`_

Managed workflow catalog and synchronization documentation belongs to
``LibreCodeCoop/.github``. Consumer repositories should use the current
organization catalog rather than copying orchestration from the retired
``github-workflows`` repository.

The remaining pages in this section describe LibreSign's concrete release
process. Generic Release Tool configuration should stay canonical in the
Release Tool repository instead of being duplicated here.
Loading