List view
This milestone reflects a series of tasks that rework the internal APIs to integrate directly with Yarn where possible to minimize yarks footprint, and the implementation of a Yarn plugin that exposes yarks task running system
No due date•0/1 issues closedThis milestone reflects a series of issues critical to ensuring yarks ecosystem is robust, maintainable, and it's common use cases are optimized to scale with both vast projects and repositories with extensive history.
No due date•0/2 issues closedThis milestone represents fleshing out the existing plugins with additional options and adding additional 'core' plugins for automating common tasks ex. creating GitHub releases. The goal here isn't to reach feature-parity with something as mature as `semantic-release`, but increase flexibility of overall application and a more comprehensive 'out of the box' experience.
No due date•0/6 issues closedThis milestone represents the initial working release of yarks and it's surrounding ecosystem, including fundamental tooling such as testing infrastructure, linting & formatting, and an automated CD pipeline.
No due date•16/30 issues closedThis milestone reflects the core release workflow being split out into distinct plugin packages that will be configurable with a centralized and workspace-specific configuration file(s), to be evaluated at runtime and coordinated by a streamlined core API.
No due date•0/3 issues closedThis milestone represents splitting yark's underlying API into multiple packages as a supportive step towards an initial plugin-driven architecture. This will include extracting the core release workflow into a package separate from the CLI, and extracting it's constituents into an organised file hierarchy with types to ensure a strong API contract & much needed unit tests.
No due date•4/7 issues closed