Repository navigation
feat: take the Pelican Panel version from GitHub at build time - #244
Merged
Merged
Conversation
…build sync-release writes data/release.json (version, date, link). 5 s timeout, one retry; any failure prints one line and leaves the committed fallback, so the build never fails or waits on GitHub.
… GitHub home-data reads data/release.json and keeps its typed rc.2 values as the fallback. The announcement bar keeps its rc.2 sentence only for rc.2.
…in a day Adds a schedule that publishes the same branches a push does, passes GITHUB_TOKEN to the build, and names the built branch and commit in BUILD.json (BUILD_SHA/BUILD_BRANCH) since the daily run starts on main.
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
One fetch with a 5-second timeout, no retry (the build already falls back and the docs rebuild daily), no custom error class or extra checks. Tests cover the release picking only. 130 lines down to 50.
The daily run only needs to rebuild pelican.dev, which a scheduled run on main already does like a push to main. Drops the branch-picking job, the matrix and the BUILD_SHA/BUILD_BRANCH plumbing in pack-docs.
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
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.
llms.txt and the homepage say Pelican Panel 1.0.0-rc.2 because the version was typed by hand, while GitHub's latest release is already rc.4 (19 November 2026). This reads the version from GitHub when the docs are built, and rebuilds them daily, so the version stays current without anyone editing it.
What changes
scripts/sync-release.mjsruns before the build and writes the latest pelican/panel release (drafts skipped, prereleases kept) todata/release.json. It has a 5 s timeout. On any failure it logs one line and the build uses the typed values inlib/home-data.ts.main. The build step getsGITHUB_TOKENso the release lookup isn't rate-limited.Checked
bun test: 165 pass.bun run typecheck: ok.bun run buildpasses;out/llms.txtsays "Current version: 1.0.0-rc.4."{}, so the build uses rc.2.Not checked
main, so it starts once Rebuild the docs on Next.js + Fumadocs under /docs, with the Worker that puts the Hub on pelican.dev #234 is merged.