Skip to content

ci: adopt shared Slidev releases and update workflows - #27

Merged
neilime merged 1 commit into
mainfrom
feat/shared-release-workflow
Nov 8, 2026
Merged

neilime merged 1 commit into
mainfrom
feat/shared-release-workflow

Conversation

@neilime

@neilime neilime commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

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/theme while keeping the example deck private. Move npm publication out of main CI and retain main-branch Pages deployment.

  • Use package.test-project: packages/slides with 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 02a04ad25ceaacdf3b7200e45fb7fec07fadf4fa for preparation, validation and publication.

Configure CI_BOT_APP_CLIENT_ID and CI_BOT_APP_PRIVATE_KEY with permission to push signed version commits/tags and dispatch the prepared workflow. Configure npm trusted publishing for this repository and release.yml, with no npm environment restriction. Any Pages environment must allow prepared release tags. CHANGELOG_SUMMARY is optional.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

Hi, thank you for creating your PR, we will check it out very soon

@github-actions github-actions Bot added the type: feature Introduces a new feature label Nov 5, 2026
@neilime
neilime force-pushed the feat/shared-release-workflow branch from ede0f18 to 820e178 Compare November 6, 2026 19:57
@neilime neilime changed the title feat(ci): adopt shared package release workflow ci(release): adopt shared Slidev theme releases Nov 6, 2026
@github-actions github-actions Bot added the type: maintenance Performs maintenance work label Nov 6, 2026
@neilime
neilime force-pushed the feat/shared-release-workflow branch 2 times, most recently from d304919 to 960d586 Compare November 8, 2026 17:55
@neilime neilime changed the title ci(release): adopt shared Slidev theme releases ci: adopt shared Slidev releases and update workflows Nov 8, 2026
@neilime
neilime force-pushed the feat/shared-release-workflow branch from 960d586 to 9597475 Compare November 8, 2026 18:42
@github-actions

github-actions Bot commented Nov 8, 2026 •

Copy link
Copy Markdown

Super-linter summary

Language Validation result
BIOME_FORMAT Pass ✅
BIOME_LINT Pass ✅
CHECKOV Pass ✅
GITHUB_ACTIONS Pass ✅
GITHUB_ACTIONS_ZIZMOR Pass ✅
GITLEAKS Pass ✅
GIT_COMMITLINT Pass ✅
GIT_MERGE_CONFLICT_MARKERS Pass ✅
JSCPD Pass ✅
MARKDOWN Pass ✅
MARKDOWN_PRETTIER Pass ✅
NATURAL_LANGUAGE Pass ✅
PRE_COMMIT Pass ✅
SPELL_CODESPELL Pass ✅
TRIVY Pass ✅
YAML Pass ✅
YAML_PRETTIER Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter
Super-linter revision: 2da136927bd4a73596db63044b504547c62cb854
Super-linter version: 9.0.0

@neilime
neilime force-pushed the feat/shared-release-workflow branch from 9597475 to 658a22b Compare November 8, 2026 18:50
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
neilime force-pushed the feat/shared-release-workflow branch from 658a22b to 5c5614e Compare November 8, 2026 19:11
@neilime
neilime marked this pull request as ready for review November 8, 2026 19:48
@neilime
neilime merged commit c4b3860 into main Nov 8, 2026
34 checks passed
@neilime
neilime deleted the feat/shared-release-workflow branch November 8, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: feature Introduces a new feature type: maintenance Performs maintenance work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant