Skip to content

Spike: Define release and changelog process #109

@lornakelly

Description

@lornakelly

Description

Investigate and define an approach for managing releases, versioning, and changelogs for the editor npm package. This includes evaluating tools and workflows for generating changelogs, handling version bumps, and publishing releases. Based on the findings, please update placeholder ticket and estimate #126

Motivation

Establish a simple, consistent process for delivering the package to npm, ensuring changes are tracked, versioned, and communicated clearly.

Proposed Implementation

Review existing examples (e.g. multi-clasp2) for reference.

Definition of Done

  • Implementation: Fully implemented according to the Serverless Workflow spec.
  • Unit Tests: Comprehensive unit tests are included and passing.
  • Integration Tests: Verified within the monorepo and target environments (Web/VS Code).
  • Documentation: Updated README.md, ADRs, or official docs.
  • Performance: No significant regression in editor responsiveness.
  • Accessibility: UI changes comply with accessibility standards.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions