Release Apache SkyWalking Horizon UI 1.0.0 - #906
Merged
Conversation
releases.yml: add 1.0.0 at the top of source and distribution, dated Aug. 28th, 2026, and demote 0.7.0's links from closer.cgi/downloads to archive.apache.org. 0.6.0 is kept. docs.yml: move Latest onto 19ca126d9bd931b51af86e31086bf615dad3decd, the v1.0.0 tag commit, and add a v1.0.0 entry carrying the same commitId so seo/doc-canonical-map.html points the versioned tree at /latest/ rather than letting the two compete. Event post condensed from docs/changelog/1.0.0.md at the tag, in the section style the 0.6.0 and 0.7.0 posts use. Verified against a local build: doc.sh checks the commitId out cleanly at "Prepare release 1.0.0" and generates the sidebar and doc tree; the built v1.0.0 doc page emits rel=canonical to /latest/readme/; the downloads page shows 1.0.0 as latest with 0.7.0 and 0.6.0 on archive, and all six archive links for those two answer 200. The 1.0.0 artifacts are committed to dist/release/skywalking/horizon-ui/ in SVN, but downloads.apache.org had not mirrored them at the time of writing, so the .asc and .sha512 links 404 until it syncs. The URLs match the filenames in SVN exactly.
✅ Deploy Preview for skywalking-website-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
Author
|
The mirror caveat above has cleared. Every download link on the page is live; nothing left to wait on. |
With 1.0.0 out, 0.7.0 and 0.6.0 come off both pages. releases.yml keeps only the 1.0.0 source and distribution rows, so the card loses its "+N more" dropdown; docs.yml keeps Next, Latest and v1.0.0. The release event posts for 0.5.0, 0.6.0 and 0.7.0 stay where they are — those are the historical announcements, and the artifacts remain on archive.apache.org for anyone who needs them.
Member
Author
|
Pushed a second commit dropping the pre-1.0 versions from both pages, now that 1.0.0 is the release.
Deliberately not removed: the release event posts for 0.5.0, 0.6.0 and 0.7.0. Those are the historical announcements rather than release pages, and the artifacts stay on Note this retires the |
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.
Horizon UI 1.0.0 was tagged and released on 2026-08-28. This updates the three places a release touches.
data/releases.ymlsourceanddistribution, datedAug. 28th, 2026.closer.cgi/downloads.apache.orgtoarchive.apache.org. 0.6.0 kept as-is — nothing was overwritten.dist/release/skywalking/horizon-ui/1.0.0/:apache-skywalking-horizon-ui-1.0.0-{src,bin}.tar.gzplus.asc/.sha512.data/docs.ymlLatestmoved to19ca126d9bd931b51af86e31086bf615dad3decd— the commit thev1.0.0tag points at.v1.0.0entry added carrying the same commitId, solayouts/partials/seo/doc-canonical-map.htmlpoints the versioned tree at/latest/instead of letting the duplicate pair compete in search.Event post
content/events/release-apache-skywalking-horizon-ui-1-0-0/index.md, condensed fromdocs/changelog/1.0.0.mdat the tag into the#####-section style the 0.6.0 and 0.7.0 posts use. The headline additions in 1.0: an AI assistant that answers from live data with real dashboard widgets, an MCP endpoint so an external agent can read the same data under the same permissions, OIDC single sign-on, and an optional login audit.Verification
Checked against a local
hugobuild rather than assumed:doc.shrun directly against the new commitId — checks out cleanly atPrepare release 1.0.0and generates both the doc tree anddata/docSidebar/skywalking_horizon_ui1_0_0.yml./docs/skywalking-horizon-ui/v1.0.0/readme/emitsrel="canonical"→/latest/readme/, confirming the shared commitId does its job.latest, with 0.7.0 and 0.6.0 in the dropdown on archive links. All six archive links for those two return 200.Next / v1.0.0 / v0.7.0 / v0.6.0; the event post is at the top of the events index.${{ ... }}anywhere indata/, and no build artifacts included —data/stars.ymlandlayouts/projectdoc/baseof.htmlare untouched, and thedoc.shoutputs land in gitignored paths.One caveat
The 1.0.0 artifacts are committed to
dist/release/skywalking/horizon-ui/1.0.0/in SVN, but at the time of writingdownloads.apache.orghad not mirrored them — it still listed only 0.7.0, so the six.asc/.sha512links for 1.0.0 return 404. The URLs are correct and match the SVN filenames exactly; this is ordinary mirror lag that clears on its own, typically within the hour. Worth a re-check before merge.