Decouple release of create-*-app packages from @inditextech-scoped packages

Open
#1,163 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start by locating the nx release configuration that versions and publishes packages under code/packages/. Trace how the two create--app packages are grouped with the @inditextech-scoped packages, then verify that each group can be versioned and published on its own without unnecessary releases for the other group.

Written by the indexing model from the issue text.

Description

enhancement

Summary

Currently nx release versions and publishes all packages under code/packages/* together, using a single fixed version (e.g. 5.3.0-SNAPSHOT). This ties the unscoped scaffolding CLIs create-weave-backend-app and create-weave-frontend-app to the exact same release cadence and version number as the @inditextech-scoped SDK packages (@inditextech/weave-sdk, @inditextech/weave-react, @inditextech/weave-types, etc.), even though the two groups have very different release needs: the CLIs mostly change to update scaffolded templates/dependencies, while the SDK packages change with core framework work.

We should decouple releases so that create-weave-backend-app and create-weave-frontend-app can be versioned and published independently from the @inditextech-scoped packages.

Motivation

Reduce release noise: publishing a new version of create-weave-backend-app/create-weave-frontend-app on every SDK release (and vice versa) creates unnecessary npm publishes, changelog entries, and git tags for packages that had no functional change.

Dominant language
TypeScript
Stars
276
Forks
26
Avg merge
1d 10h
Merged PRs (30d)
47

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InditexTech/weavejs

All issues in InditexTech/weavejs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.