Release Apache SkyWalking Helm Chart 5.0.0 and SWCK 0.11.0 - #912
Merged
Conversation
releases.yml: add helm 5.0.0 and swck 0.11.0 at the top of their sections, dated Sep. 1st, 2026, and demote 4.9.0 and 0.10.0 to archive.apache.org. All 21 links verified to return 200. SWCK 0.11.0 ships its Helm chart as a signed, voted artifact for the first time (skywalking-swck-0.11.0.tgz, absent from 0.10.0), so it is listed beside the binary tarball using the "|" separator pattern the GraalVM distro card already uses. Without it the new artifact would be invisible on the site. Two event posts, each in its component's established style: the Helm one keeps the release's Breaking changes / Features / Corrections structure, the SWCK one the Features / Bugs / Chores shape its earlier posts use. Per the repo's rules the release-tooling, e2e and dependency-bump entries are left out of the SWCK post, which was most of its changelog's volume. docs.yml already points at these versions from #910, so the docs and downloads pages now agree — the gap noted there is closed. Note the posts are dated 2026-09-01. Hugo does not build future-dated content and buildFuture is unset, so merging before Sep 1 10:00 UTC leaves the two event pages ungenerated until the next daily scheduled build picks them up. The downloads page updates immediately either way, since its dates are plain display strings.
✅ Deploy Preview for skywalking-website-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wu-sheng
added a commit
that referenced
this pull request
Aug 31, 2026
) skywalking-helm-<version>.tgz — the packaged chart, and the artifact people actually install — is published to the ASF dist but was never linked. The Kubernetes Helm card carried a Source section alone, offering only the source tarball, so the chart was reachable only by browsing the mirror by hand. Adds a Distribution section with the chart for 5.0.0 (closer.cgi plus downloads.apache.org signatures) and 4.9.0 (archive), labelled "Helm chart" to match what the SWCK card already shows. All six links verified to return 200. This is a standing omission rather than something 5.0.0 introduced — 4.9.0 shipped the chart too. It became visible now because SWCK 0.11.0 started publishing its own chart in #912, leaving two adjacent cards disagreeing about whether a released chart gets a link.
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.
Both releases are published to the ASF dist, so this brings the downloads page and the event log up to date.
data/docs.ymlalready points at these versions from #910, which closes the gap noted there — docs and downloads now agree.data/releases.ymlSep. 1st, 2026Sep. 1st, 2026Older versions are kept, not replaced. All 21 download links probed — every one returns 200, both the new
closer.cgi/downloads.apache.orglinks and the demotedarchive.apache.orgones.SWCK 0.11.0 ships its Helm chart as a signed, voted artifact for the first time —
skywalking-swck-0.11.0.tgz, which 0.10.0 did not have, and which its release notes call out explicitly. It would have been invisible on the site, so it is listed beside the binary tarball using the"|"separator pattern the GraalVM distro card already uses. It renders as a second row, "Helm chart ↓ / asc / sha512".Event posts
One each, following the style that component's own previous posts use — the Helm post keeps the release's
Breaking changes / Features / Correctionsstructure, the SWCK post theFeatures / Bugs / Choresshape. Per the repo's rules I left the release-tooling, e2e and dependency-bump entries out of the SWCK post; they were the bulk of its changelog but none are user-facing.The posts are dated
2026-09-01, and Hugo does not build future-dated content.buildFutureis unset inconfig.toml, so if this merges before Sep 1, 10:00 UTC the two event pages are simply not generated — the build still passes, and the downloads page updates immediately since its dates are plain display strings, but the announcements will not appear until the next daily scheduled build (cron: 0 10 * * *) after that date.Nothing breaks — there are no dangling links to them, they just do not exist yet. If you would rather they were live the moment this merges, change the two
date:fields to2026-08-31and I can push that; theSep. 1st, 2026release dates on the downloads page can stay either way.Verification
Full Hugo build; downloads cards confirmed showing 5.0.0 and 0.11.0 as LATEST with the previous versions behind "+1 more", the new dates rendering as
Sep. 1st, 2026, and the SWCK card carrying the extra Helm chart row. No${{ }}anywhere indata/, and no generated artifacts included.