Skip to content

docs: install the collections from Galaxy and the chart from Artifact Hub - #153

Merged
thiras merged 2 commits into
mainfrom
docs/released-artifacts
Oct 13, 2026
Merged

thiras merged 2 commits into
mainfrom
docs/released-artifacts

Conversation

@thiras

@thiras thiras commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

All three artifacts are published (decdn.node 0.1.0 and decdn.publisher 0.1.0 on Galaxy, the decdn-node chart on oci://ghcr.io/decdn/charts and Artifact Hub), but the docs still described them as unreleased.

  • Collection READMEs (the Galaxy pages): install from Galaxy first; building from a checkout is now only for unreleased changes, and the 0.0.0 / --no-deps workaround is gone.
  • Chart README (the Artifact Hub page): the OCI install comes first, with links to Artifact Hub and the CHANGELOG.
  • README: Galaxy badges for both collections, and the deploy table links Galaxy and Artifact Hub. docs/node-operators.md and docs/publishers.md give the install commands.
  • CONTRIBUTING / AGENTS / ansible/README: removed the "log under [Unreleased] by hand until the first release" instruction. Changelogs are now always generated.
  • RELEASING: PUBLISH_ENABLED is on and the one-time setup is done. The first-release mechanics are kept for any new artifact. No script changes.

The collection and chart READMEs ship in the packages, so these changes reach Galaxy and Artifact Hub with each artifact's next release.

Checked: make lint, make test-scripts, make galaxy-check, make lint-helm. Every new external link and badge returns 200.

🤖 Generated with Claude Code

… Hub

decdn.node and decdn.publisher 0.1.0 are on Galaxy and the decdn-node
chart is on oci://ghcr.io/decdn/charts and Artifact Hub, so make those
the install path everywhere: drop the "Not on Galaxy yet" boxes and the
0.0.0 --no-deps workaround from the collection READMEs, lead the chart
README with the OCI install, link Galaxy and Artifact Hub from the
README (plus Galaxy badges) and the operator front doors.

Drop the "until the first release, log under [Unreleased] by hand"
instructions from CONTRIBUTING, AGENTS and ansible/README, and note in
RELEASING that PUBLISH_ENABLED is on and the one-time setup is done.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 13, 2026 15:38

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Checkout installs need forced replacement, and the changelog guidance conflicts with the documented first-release process.

3 open findings
What changed in this PR

Updates deployment documentation now that the Galaxy collections and Helm chart are published.

Changes:

  • Prioritizes Galaxy and OCI installation paths.
  • Adds artifact links and badges.
  • Updates release and changelog guidance.
File Description
RELEASING.md Records completed publishing setup.
README.md Adds artifact badges and links.
docs/​publishers.md Documents publisher collection installation.
docs/​node-operators.md Links published node artifacts.
CONTRIBUTING.md Updates changelog guidance.
charts/​decdn-node/​README.md Prioritizes OCI installation.
ansible/​README.md Links published collections.
ansible/​galaxy/​publisher/​README.md Replaces prerelease installation guidance.
ansible/​galaxy/​node/​README.md Replaces prerelease installation guidance.
AGENTS.md Records current release state.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CONTRIBUTING.md Outdated
Comment thread ansible/galaxy/node/README.md Outdated
Comment thread ansible/galaxy/publisher/README.md Outdated
…ule for a new artifact

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@thiras
thiras merged commit 0434bc1 into main Oct 13, 2026
54 checks passed
@thiras
thiras deleted the docs/released-artifacts branch October 13, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants