Repository navigation
chore(root): point repository links at videojs/video.js - #9253
Conversation
Video.js 10 moved from videojs/v10 into videojs/video.js. Point repository, issue, discussion, release-download, and contributing links at the new home. Links to specific v10 PRs, issues, commits, and compare ranges stay on videojs/v10, which still resolves them and whose numbers collide with unrelated videojs/video.js PRs. git-cliff now links PRs numbered 9248 and up to videojs/video.js and lower numbers to videojs/v10.
Merging the Video.js 8 history into main made git-cliff treat v8 tags as releases and pull untagged v8 commits into the next Video.js 10 section. Match only @videojs/core tags and hide the merged v8 tip from the commit range in the release workflow and the changelog script.
❌ Deploy Preview for vjs10-site failed. Why did it fail? →
|
✅ Deploy Preview for vjs-registry ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@videojs/cdn
@videojs/cli
@videojs/core
@videojs/element
@videojs/html
@videojs/media
@videojs/react
@videojs/spf
@videojs/store
@videojs/utils
@videojs/cloudflare-video
@videojs/dash-video
@videojs/hlsjs-video
@videojs/mux-audio
@videojs/mux-video
@videojs/native-hls-video
@videojs/shaka-video
@videojs/spotify-audio
@videojs/tiktok-video
@videojs/twitch-video
@videojs/vimeo-video
@videojs/wistia-video
@videojs/youtube-video
@videojs/google-cast
@videojs/mux-data
commit: |
📦 Bundle Size Report🎨 @videojs/html — no changesPresets (7)
Media (18)
Players (5)
Skins (41)
UI Components (62)
⚛️ @videojs/react — no changesPresets (7)
Media (22)
Extensions (2)
Players (5)
Skins (26)
UI Components (39)
🧩 @videojs/core — no changesEntries (76)
🏷️ @videojs/element — no changesEntries (2)
📦 @videojs/store — no changesEntries (3)
🔧 @videojs/utils — no changesEntries (13)
📦 @videojs/cdn — 1 small size change
📦 @videojs/cloudflare-video — no changes📦 @videojs/dash-video — no changes📦 @videojs/google-cast — no changes📦 @videojs/hlsjs-video — no changes📦 @videojs/media — no changesEntries (3)
📦 @videojs/mux — no changes📦 @videojs/mux-audio — no changesEntries (2)
📦 @videojs/mux-data — no changes📦 @videojs/mux-video — no changesEntries (2)
📦 @videojs/native-hls-video — no changes📦 @videojs/shaka-video — no changes📦 @videojs/spf — no changesEntries (7)
📦 @videojs/spotify-audio — no changes📦 @videojs/tiktok-video — no changes📦 @videojs/twitch-video — no changes📦 @videojs/other — 1 small size change
Entries (3)
📦 @videojs/vimeo-video — no changes📦 @videojs/wistia-video — no changesEntries (2)
📦 @videojs/youtube-video — no changesℹ️ How to interpretEach entry is independently bundled, minified, and brotli-compressed. Initial size includes its static import graph; lazy dynamic chunks are reported separately. Entries are not additive because their dependency graphs overlap. Preset rows represent realistic combined bundles. Changes of 300 B or less across initial, lazy, and total size are collapsed, not discarded. Run |
cjpillsbury
left a comment
There was a problem hiding this comment.
🚀 one question on the added for the commit_preprocessor bits, but pre-approving.
| # Replace issue numbers with link templates to be updated in `changelog.postprocessors`. | ||
| #{ pattern = '\((\w+\s)?#([0-9]+)\)', replace = "([#${2}](<REPO>/issues/${2}))"}, | ||
| # Replace (#NNN) with a Markdown link to the GitHub PR. | ||
| # Replace (#NNN) with a Markdown link to the GitHub PR. Video.js 10 was developed in |
There was a problem hiding this comment.
question(non-blocking): I don't understand what's going on here. Is this permanently needed? Temporarily needed? Only for bridging to the v10 repo?
There was a problem hiding this comment.
Answered out of band: TL;DR - changelog for already merged changes refer to PRs in v10. This accounts for that.
Summary
Video.js 10 moved from
videojs/v10intovideojs/video.js. This points repository-level links at the new home and stops the root changelog from absorbing the merged Video.js 8 history.Changes
videojs/video.js: packagerepositoryfields, READMEs,CONTRIBUTING.md, the site'sGITHUB_REPO_URL(nav, footer, edit-page, search, support), docs guides, the sandbox navbar, and the changelog-prose script defaults.videojs/v10. That repo still resolves them, and its numbers collide with unrelatedvideojs/video.jsPRs (for example, video.js Added lang: pl.json #3127 is a 2016 language-file PR).videojs/video.jsand lower numbers tovideojs/v10, and its compare links usevideojs/video.js(all@videojs/core@*tags exist there).@videojs/core@*tags, and the release workflow andchangelogscript hide the merged v8 tip from the commit range via the newhistory/v8-tiptag (1aea7c9, already pushed). Without this, v8 tags became changelog sections and untagged v8 commits leaked into the next 10.x release.Known tradeoff
git-cliff now reads GitHub metadata from
videojs/video.js, so regenerated "New Contributors" blocks in older rootCHANGELOG.mdsections lose their v10 PR links, and long-time video.js contributors drop off. The site only uses the current release's list, which the prose workflow turns into a thank-you sentence.history/v8-tipmarks a fixed commit; if8.xis ever merged intomainagain, move the tag to the new tip or hide that tip too.Testing
pnpm -F site testfor the link-analytics, Mux attribution, and link-destination tests (18 passed).pnpm check:workspace(11 passed).videojs/v10, and docs(root): add security policy and v8 issue routing #9248 linked tovideojs/video.js.