Skip to content

Serve Latest from the project, and build 0.5.0 documentation from docs/v0.5.0 - #938

Merged
wu-sheng merged 2 commits into
masterfrom
asz-0.5.0-docs-branch
Sep 24, 2026
Merged

wu-sheng merged 2 commits into
masterfrom
asz-0.5.0-docs-branch

Conversation

@wu-sheng

@wu-sheng wu-sheng commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

Two changes to data/projects.yml, the second one a schema change.

AI Sessionizer 0.5.0 documentation. The numbered and the Latest documentation now build from the head of docs/v0.5.0 (532cc2de) instead of the v0.5.0 tag (8743b2cb), as 0.4.0's build from docs/v0.4.0. That branch is the tag with documentation fixes only: the parts of apache/skywalking-ai-sessionizer#38 that apply to 0.5.0, and what a set source_root means for claude-code-local.

Latest is configured on the project, and renders the latest release's own pin. A release carried latestLink and latestCommitId, so the Latest tree was configured once per release and its pin was a second copy of the release pin. The project now says where its two generated trees live:

        docs:
          link: /docs/skywalking-ai-sessionizer/next/readme/
          latest: /docs/skywalking-ai-sessionizer/latest/readme/
        releases:
          - version: v0.5.0
            latest: true
            docs:
              link: /docs/skywalking-ai-sessionizer/v0.5.0/readme/
              commitId: 532cc2de7c0443290817ab5fa211ffdcac151a14

Latest renders the commitId of the release marked latest: true, so a release carries one pin and the two can never disagree. The project-level next block is gone and its keys moved into docs; data/get-started.yml follows for the Showcase. The validator now rejects latestLink and latestCommitId by name, and requires a commitId on the latest release when the project serves Latest.

One project's pins had drifted. skywalking-go served Latest from 41a66149 while v0.7.0 served the tag b52ef576. v0.7.0 now pins 41a66149, the documentation commit Latest already served, so the numbered tree gains the same fixes and no published page changes.

Checked: node scripts/project-config.js and npm test pass (10 tests, updated for the new shape). The entries deriveDocsList generates are byte-identical to master's apart from the three intended pins above — same 50 projects, same 81 documentation entries, same Latest URLs. A local Hugo build serves the same documentation links as the live site on /docs/ (65), /downloads/ (33), /get-started/ (2) and the home page (9).

Follow-up, not in this PR: tools/release/release.sh in apache/skywalking-ai-sessionizer writes website.txt with latestLink and latestCommitId, so it needs a matching update.

The numbered and the Latest documentation of 0.5.0 now build from the
head of docs/v0.5.0 in apache/skywalking-ai-sessionizer, as 0.4.0's build
from docs/v0.4.0. It is the v0.5.0 tag with documentation fixes only: the
parts of #38 there that apply to 0.5.0, and what a set source_root means
for claude-code-local.
@netlify

netlify Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for skywalking-website-preview ready!

Name Link
🔨 Latest commit 50c6dde
🔍 Latest deploy log https://app.netlify.com/projects/skywalking-website-preview/deploys/6ab52787891dad000915d19c
😎 Deploy Preview https://deploy-preview-938--skywalking-website-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

A release carried latestLink and latestCommitId, so the Latest tree was
configured once per release and its pin was a second copy of the release
pin. They could drift, and in skywalking-go they had: Latest served
41a66149 while v0.7.0 served the tag.

The project now says where its two generated trees live:

    docs:
      link: /docs/skywalking-go/next/readme/
      latest: /docs/skywalking-go/latest/readme/

Latest renders the commitId of the release marked latest, so a release
carries one pin and the two cannot disagree. The project-level next block
is gone; its keys moved to docs. skywalking-go v0.7.0 now pins 41a66149,
the documentation commit its Latest tree already served, so the numbered
tree gains the same fixes and no page changes.

The validator rejects the retired keys by name, and requires a commitId
on the latest release when the project serves Latest.
@wu-sheng wu-sheng changed the title Build the AI Sessionizer 0.5.0 documentation from docs/v0.5.0 Serve Latest from the project, and build 0.5.0 documentation from docs/v0.5.0 Sep 24, 2026
@wu-sheng
wu-sheng merged commit 3391ad5 into master Sep 24, 2026
4 of 5 checks passed
@wu-sheng
wu-sheng deleted the asz-0.5.0-docs-branch branch September 24, 2026 13:41
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.

1 participant