pleroma/api-docs
Watch
0
0
Fork
You've already forked api-docs
 2
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity

Woodpecker CI: Reimplement Gitlab api docs deployment pipeline #5

Merged
lambadalambda merged 2 commits from woodpecker-ci into master 2026-09-09 11:00:54 +00:00
Conversation 3 Commits 2 Files changed 1 +68
phnt commented 2026-06-21 16:04:41 +00:00
Member
Copy link
  • new secrets (all same contents as on Gitlab):
    • pleroma-ci-docs-host-key
    • pleroma-ci-docs-ssh-port
    • pleroma-ci-docs-priv-key
    • pleroma-ci-docs-host-location (repo specific, docs uses same secret name)
  • Deployments need to be enabled for this repository for the trigger in pleroma/pleroma to work (pleroma/pleroma!7928)
* new secrets (all same contents as on Gitlab): - pleroma-ci-docs-host-key - pleroma-ci-docs-ssh-port - pleroma-ci-docs-priv-key - pleroma-ci-docs-host-location (**repo specific, docs uses same secret name**) * Deployments need to be enabled for this repository for the trigger in pleroma/pleroma to work (pleroma/pleroma!7928)
phnt commented 2026-06-21 16:42:59 +00:00
Author
Member
Copy link

Uploaded a spec.json from Pleroma 2.10.2 as a package, so this can be merged before the MR in pleroma/pleroma

Uploaded a `spec.json` from Pleroma 2.10.2 as a package, so this can be merged before the MR in pleroma/pleroma
lambadalambda commented 2026-09-09 09:23:05 +00:00
Owner
Copy link

Release-readiness fixes pushed in 127af92:

  • serialize deployments
  • validate BRANCH as stable or develop
  • accept a channel alias or exact lowercase 40-character SHA as SPEC_VERSION
  • use the immutable SHA supplied by the parent trigger while preserving channel defaults for direct runs
  • deploy the complete site/ tree (including dotfiles) to the channel-specific destination

Validated with Woodpecker 3.18.0 strict lint, YAML/static acceptance checks, shell validation, and git diff --check. An independent review found no remaining release-blocking issues.

This child workflow should merge before pleroma/pleroma #7928.

Release-readiness fixes pushed in `127af92`: - serialize deployments - validate `BRANCH` as `stable` or `develop` - accept a channel alias or exact lowercase 40-character SHA as `SPEC_VERSION` - use the immutable SHA supplied by the parent trigger while preserving channel defaults for direct runs - deploy the complete `site/` tree (including dotfiles) to the channel-specific destination Validated with Woodpecker 3.18.0 strict lint, YAML/static acceptance checks, shell validation, and `git diff --check`. An independent review found no remaining release-blocking issues. This child workflow should merge before pleroma/pleroma #7928.
lambadalambda commented 2026-09-09 12:57:46 +00:00
Owner
Copy link

Merged and live-validated. Stable push pipeline 4 and immutable-SHA develop deployment pipeline 6 both passed. api.pleroma.social and api-develop.pleroma.social return HTTP 200 with valid TLS and distinct channel content.

Merged and live-validated. Stable push pipeline 4 and immutable-SHA develop deployment pipeline 6 both passed. `api.pleroma.social` and `api-develop.pleroma.social` return HTTP 200 with valid TLS and distinct channel content.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pleroma/api-docs!5
No description provided.