Skip to content

chore(build): remove content pipeline check - #544

Merged
Dawn6666666 merged 1 commit into
LyraVoid:masterfrom
Dawn6666666:chore/remove-content-pipeline-check
Aug 8, 2026
Merged

chore(build): remove content pipeline check#544
Dawn6666666 merged 1 commit into
LyraVoid:masterfrom
Dawn6666666:chore/remove-content-pipeline-check

Conversation

@Dawn6666666

Copy link
Copy Markdown
Collaborator

Type of change

  • Bug fix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Other (please describe):

Checklist

  • I have read the CONTRIBUTING document.
  • I have checked to ensure that this Pull Request is not for personal changes.
  • I have performed a self-review of my own code.
  • My changes generate no new warnings.

Related Issue

None.

Changes

Remove node scripts/check-content-pipeline.mjs from the production build command. This prevents content-separated builds from failing when the upstream content-pipeline fixture is not present in the personal content repository.

The checker script and its tests are left unchanged; only its automatic build invocation is removed.

How To Test

Not run, as requested.

Screenshots (if applicable)

Not applicable.

Additional Notes

This PR changes only package.json.

Copilot AI lite review requested due to automatic review settings August 8, 2026 14:55

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@Dawn6666666
Dawn6666666 merged commit b5776e4 into LyraVoid:master Aug 8, 2026
3 checks passed
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