Skip to content

Fix/pipeline exports#394

Open
pipewrk wants to merge 4 commits intowpkernel:fix/pipeline-exportsfrom
theGeekist:fix/pipeline-exports
Open

Fix/pipeline exports#394
pipewrk wants to merge 4 commits intowpkernel:fix/pipeline-exportsfrom
theGeekist:fix/pipeline-exports

Conversation

@pipewrk
Copy link
Contributor

@pipewrk pipewrk commented Dec 24, 2025

No description provided.

@coderabbitai
Copy link

coderabbitai bot commented Dec 24, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 1 to 6
export * from './runner';
export { OFFICIAL_EXTENSION_BLUEPRINTS } from './official';
// Export official blueprints from a dedicated entry point to avoid bundling them
// with core logic (they contain large documentation strings).
export type {
OfficialExtensionBlueprint,
ExtensionBlueprint,

Choose a reason for hiding this comment

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

P1 Badge Re-expose official extension blueprints on extensions entry

The extensions entry point no longer exports OFFICIAL_EXTENSION_BLUEPRINTS, leaving @wpkernel/pipeline/extensions with only type exports while the README still directs consumers to import the blueprint list from that subpath. Any existing code doing import { OFFICIAL_EXTENSION_BLUEPRINTS } from '@wpkernel/pipeline/extensions' will now fail to compile because the symbol is missing, even though it is still exported from the package root. Please keep the constant available from the documented extensions entry (or provide a replacement entry) to avoid breaking consumers.

Useful? React with 👍 / 👎.

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.

1 participant