feat: add pipelines v1

[luxass]

🔗 Linked issue

📚 Description

[changeset-bot]

⚠️ No Changeset found

Latest commit: dbd7636

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Draft detected.

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.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/pipelines-v1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

In general, to avoid incomplete escaping or cleaning when using String.prototype.replace, use a global regular expression (/.../g) or another method that processes all occurrences (e.g., split/join) instead of passing a plain string, which only affects the first occurrence.

Here, the goal is to normalize rangeName by stripping the trailing ", First>" marker and removing all < characters from the remaining name. The current code:

if (characterName.endsWith(", First>")) {
  rangeStart = codePoint;
  rangeName = characterName.replace(", First>", "").replace("<", "");
  continue;
}

only removes the first <. The most direct, non-functional-change fix is to change the second .replace to use a global regular expression:

rangeName = characterName.replace(", First>", "").replace(/</g, "");

This preserves the existing behavior for typical inputs (with a single <), but correctly handles any unexpected extra < characters. No new imports or helpers are needed, and the change is localized to line 48 in packages/pipelines/pipeline-presets/src/parsers/unicode-data.ts.

[github-actions]

🌏 Preview Deployments

Application	Status	Preview URL
API	⏳ In Progress	N/A
Website	⏳ In Progress	N/A
Documentation	⏳ In Progress	N/A

Built from commit: 483558979674341c86d594785cb093ce445ef126

---

_{🤖 This comment will be updated automatically when you push new commits to this PR.}

In general, when building a regular expression via a string (including template literals), any regex escape like \s, \d, \w, etc., must be written with a double backslash (\\s, \\d, \\w) so that the JavaScript string literal produces a single backslash for the regex engine. Here, the pattern is intended to match something like route : "some/path" with optional whitespace around the colon. Currently it uses \s* in a template string, which evaluates to s*, so the regular expression does not match whitespace as intended.

The best minimal fix that preserves existing functionality is to escape the backslash before s, changing \s* to \\s* inside the template literal. We only adjust the whitespace sequences and leave all other parts of the pattern as-is. Specifically, in packages/pipelines/pipeline-server/src/client/routes/pipelines.$id.code.tsx at line 51, update the RegExp construction to:

const routePattern = new RegExp(`route\\s*:\\s*["']${highlightRoute}["']`, "i");

This change requires no new imports or helpers; it simply corrects the escape sequence in the existing string.