Skip to content

Release Apache SkyWalking Python 1.3.0 - #896

Merged
wu-sheng merged 1 commit into
masterfrom
rel-python-1.3.0
Aug 14, 2026
Merged

Release Apache SkyWalking Python 1.3.0#896
wu-sheng merged 1 commit into
masterfrom
rel-python-1.3.0

Conversation

@kezhenxu94

Copy link
Copy Markdown
Member

Release Apache SkyWalking Python 1.3.0

@netlify

netlify Bot commented Aug 14, 2026

Copy link
Copy Markdown

Deploy Preview for skywalking-website-preview failed.

Name Link
🔨 Latest commit a5c4ae5
🔍 Latest deploy log https://app.netlify.com/projects/skywalking-website-preview/deploys/6a7ed04e274845000855ebc6

@wu-sheng
wu-sheng merged commit 6ea2403 into master Aug 14, 2026
0 of 5 checks passed
@wu-sheng
wu-sheng deleted the rel-python-1.3.0 branch August 14, 2026 15:57
wu-sheng added a commit that referenced this pull request Aug 15, 2026
#897)

The 1.3.0 release commit (#896) was generated with un-interpolated GitHub
Actions template syntax, which broke the site build and published wrong
metadata:

- data/docs.yml carried `commitId: ${{ steps.release.outputs.commit-id }}`
  verbatim. docs.js shells that value into `./doc.sh`, so /bin/sh reported
  "Bad substitution" and the scheduled Build site workflow has failed on
  every run since the merge. Both entries now point at 1bd4692, the v1.3.0
  tag commit.
- The v1.2.0 docs entry had been overwritten rather than a v1.3.0 entry
  inserted, leaving version `1.3.0` (no v prefix) linked to the v1.2.0
  path. Restore v1.2.0 and add a proper v1.3.0 entry.
- data/releases.yml replaced the 1.2.0 download links instead of demoting
  them to archive.apache.org, so 1.2.0 was no longer downloadable. Demote
  1.2.0 and keep v1.3.0 on closer.cgi/downloads.apache.org.
- The event post rendered as "Release Apache SkyWalking Python " with an
  empty version everywhere, including a broken PyPI link
  (apache-skywalking//), and listed no changes. Rewrite it with the 1.3.0
  release notes, and rename the directory to the dashed slug convention
  used by every other release post.
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