Skip to content

[Feature Request] Introduce more frequent or Patch releases for urgent fixes or release main branch with next version #660

@itsmnthn

Description

@itsmnthn

🚀 Feature Request Description

We would like to request a mechanism for shipping urgent fixes from the main branch more quickly, rather than having to wait for the next formal release cycle. Even though the current release is sourced from main, there are situations where important fixes are merged, but developers cannot benefit from these fixes right away due to release delays.

Motivation

Is your feature request related to a problem? Please describe your use case.
Sometimes critical or time-sensitive fixes are merged into main, yet they only become publicly available when the maintainers decide to publish the next version or patch. Until that happens, developers must either wait or resort to non-ideal workarounds (like building from main manually), which complicates dependency management and can lead to inconsistent environments.

For example we've waited 3 weeks for the 1.36.0 release and #647 to become available without this Script Composer was broken.

Pitch

Describe the solution you would like

  • A more frequent or scheduled patch release process (e.g., a weekly or bi-weekly patch release if there are critical changes). or
  • An option to release “hotfix” versions that explicitly target critical issues soon after they are merged. or
  • Automatic or semi-automatic build pipelines that publish patch or minor versions as soon as a fix is merged and validated. or
  • A @aptos-labs/ts-sdk@next release from main to always have latest changes published

Describe alternatives you've considered

  • Maintaining a custom fork that includes the fix (inefficient and risky).
  • Pulling directly from the commit on main (creates maintenance overhead and can lead to unforeseen issues if main has other untested changes).
  • Waiting for the official release (can slow down development teams that need time-sensitive fixes).

Are you willing to open a pull request? (See CONTRIBUTING)
Yes, but this depends on you guys.

Additional context

Having a more streamlined approach for publishing urgent or minor or next updates will help the broader developer community stay on top of critical fixes without resorting to workarounds. This ensures higher stability for everyone using the Aptos TS SDK.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions