Reduce registry-assets publish CI memory pressure #345

Closed
opened 2026-06-06 18:41:25 +00:00 by steve · 0 comments
Owner

Describe the issue.

Problem

Goal

Scope

Non-goals

Acceptance Criteria

Implementation Notes

Suggested Files or Specs To Inspect

Validation Commands

Follow-up Tasks

Implementation Summary

Publish CI now uses lapis-ci-job-env profile publish (TURBO_CONCURRENCY=1, NODE_OPTIONS=4096). registry-assets:publish builds one official plugin package per turbo invocation so heavy Vite builds release memory between plugins. Updated workflow, composite action, script tests, and monorepo-scripts spec. Validated with pnpm test:scripts and pnpm check:all.

Describe the issue. ## Problem ## Goal ## Scope ## Non-goals ## Acceptance Criteria ## Implementation Notes ## Suggested Files or Specs To Inspect ## Validation Commands ## Related Issues - Follow-up to #338 — [Use Turbo remote cache for registry-assets:publish builds](../closed/338-use-turbo-remote-cache-for-registry-assets-publish-builds.md) ## Follow-up Tasks ## Implementation Summary Publish CI now uses lapis-ci-job-env profile publish (TURBO_CONCURRENCY=1, NODE_OPTIONS=4096). registry-assets:publish builds one official plugin package per turbo invocation so heavy Vite builds release memory between plugins. Updated workflow, composite action, script tests, and monorepo-scripts spec. Validated with pnpm test:scripts and pnpm check:all. <!-- backlog:task_id=TASK-PLUGINS-REGISTRY-009 source_spec=spec/src/80-maintenance/monorepo-scripts.md related_issue=338 -->
steve added this to the Full Registry V1 milestone 2026-06-06 18:41:25 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lapis-notes/lapis#345
No description provided.