[Internal] Rework and document release management strategy for branches

Created on 8 April 2025, 17 days ago

Problem/Motivation

While making the latest release, I (@star-szr) ran into some pain points and things that were not documented for making a new minor or major release.

Proposed resolution

  1. Add a new yarn bump-check script to output the type of version bump that would occur with the commits since the most recent tag (patch, minor, or major?).
  2. Document the process of making a new minor or major release.

Remaining tasks

  1. Create the new yarn script.
  2. Write up new RELEASING documentation that includes instructions for making a new minor or major release.
📌 Task
Status

Active

Version

1.1

Component

Miscellaneous

Created by

🇨🇦Canada star-szr

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024