Repository navigation
ci: adopt shared Slidev releases and update workflows - #27
Merged
Merged
Conversation
|
Hi, thank you for creating your PR, we will check it out very soon |
neilime
force-pushed
the
feat/shared-release-workflow
branch
from
November 6, 2026 19:57
ede0f18 to
820e178
Compare
neilime
force-pushed
the
feat/shared-release-workflow
branch
2 times, most recently
from
November 8, 2026 17:55
d304919 to
960d586
Compare
neilime
force-pushed
the
feat/shared-release-workflow
branch
from
November 8, 2026 18:42
960d586 to
9597475
Compare
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
neilime
force-pushed
the
feat/shared-release-workflow
branch
from
November 8, 2026 18:50
9597475 to
658a22b
Compare
Adopt shared release preparation and validated theme publication. Build an isolated consumer deck with the Pages base path, align package versions, and retain main-branch Pages deployment. Pin GitHub Actions and reusable workflows to current stable releases. Adapt workflow permissions and repository-configured PR title validation.
neilime
force-pushed
the
feat/shared-release-workflow
branch
from
November 8, 2026 19:11
658a22b to
5c5614e
Compare
neilime
marked this pull request as ready for review
November 8, 2026 19:48
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.
Release the public Slidev theme through shared manual/weekly preparation, validation, and publication. Validate the tarball by building the example deck as an isolated consumer.
Changes
Run release labeling only on pull request events. Keep preparation, validation and publication as separate jobs; skip validation/publication when no release is planned.
Use GitHub self-repository references (
$/) for local actions and reusable workflows.Pin every external GitHub Action and reusable workflow to its latest stable release commit, including ci-github-common 2.0.2 and ci-github-publish 3.0.0. Use repository-configured PR-title validation with only
contents: read.Pass the reporting permissions required by the shared linter through all CI callers.
Prepare
packages/themewhile keeping the example deck private. Move npm publication out of main CI and retain main-branch Pages deployment.Use
package.test-project: packages/slideswith the existing Pages base path. Share consumer setup, installation, and cleanup through the package test action.Align the manifest and lockfile with the published version, retain PR release labeling, and document the release GitHub App, npm trusted publishing, optional summaries, force, and recovery.
Keep editor-generated SVG artwork outside the code-lint scope in the root Biome configuration. Source-code linting remains enabled.
Validation
Release trigger, manual force, no-change gate, validation dependency, configuration and artifact-handoff checks pass against the released shared workflows.
Actionlint, YAML formatting,
git diff --check, and released action/workflow input, output, secret, and permission contracts pass locally. The CI checks run source tests and package validation against the pinned shared implementation.Before merging
Uses released ci-github-nodejs 2.1.0, pinned to
02a04ad25ceaacdf3b7200e45fb7fec07fadf4fafor preparation, validation and publication.Configure
CI_BOT_APP_CLIENT_IDandCI_BOT_APP_PRIVATE_KEYwith permission to push signed version commits/tags and dispatch the prepared workflow. Configure npm trusted publishing for this repository andrelease.yml, with no npm environment restriction. Any Pages environment must allow prepared release tags.CHANGELOG_SUMMARYis optional.