Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/amanvarshney01/create-better-t-stack/llms.txt

Use this file to discover all available pages before exploring further.

​
Release Notes

Better-T-Stack follows semantic versioning and maintains detailed release notes for every version.

View All Releases

See the complete changelog on GitHub Releases

​
Current Version

The latest stable version of Better-T-Stack is v3.22.0. 
# Always use the latest version
npm create better-t-stack@latest

# Check installed version
npx create-better-t-stack --version

​
Versioning Strategy

Better-T-Stack follows Semantic Versioning (SemVer): 
MAJOR.MINOR.PATCH
  • MAJOR (e.g., 1.0.0 → 2.0.0) - Breaking changes that require migration
  • MINOR (e.g., 1.0.0 → 1.1.0) - New features, backward compatible
  • PATCH (e.g., 1.0.0 → 1.0.1) - Bug fixes, backward compatible

​
Examples

  • 3.22.0 → 3.22.1 - Bug fix, safe to upgrade
  • 3.22.0 → 3.23.0 - New feature, safe to upgrade
  • 3.22.0 → 4.0.0 - Breaking changes, review before upgrading

​
Release Channels

​
Stable (Latest)

Recommended for all users: 
npm create better-t-stack@latest
  • Fully tested and stable
  • Production-ready
  • Semantic versioning guarantees

​
Canary (Bleeding Edge)

For testing upcoming features: 
npm create better-t-stack@canary
  • Latest development builds
  • May contain bugs or breaking changes
  • Not recommended for production
  • Useful for testing new features early
Canary releases are experimental and may change without notice. Use only for testing.

​
How to Stay Updated

​
Check for Updates

Always use @latest to get the newest version: 
npm create better-t-stack@latest
The CLI automatically uses the latest version when you run it with your package manager.

​
Watch the Repository

Get notified of new releases:
1

Visit the GitHub repository

Go to github.com/AmanVarshney01/create-better-t-stack
2

Click 'Watch' in the top-right

Select your notification preferences
3

Choose 'Custom' and enable 'Releases'

You’ll receive notifications for new releases only

​
Subscribe to Release Notes

You can also:
  • GitHub Releases RSS: https://github.com/AmanVarshney01/create-better-t-stack/releases.atom
  • GitHub Watch: Get email notifications for releases
  • Star the repo: Stay updated in your GitHub feed

​
Release Process

Better-T-Stack follows a structured release process:
1

Development

Features and fixes are developed on feature branches and merged to main via pull requests.
2

Version Bump

The version is bumped using bun run bump which updates package versions across the monorepo.
3

Changelog Generation

Release notes are generated using changelogithub from commit history.
4

Publish to npm

The CLI package is published to npm with bun run release.
5

GitHub Release

A GitHub release is created with detailed release notes and changelog.

​
Reading Release Notes

Each release includes:
  • Version number - The new version (e.g., v3.22.0)
  • Release date - When it was published
  • Changes summary - High-level overview of what’s new
  • Detailed changelog - All commits included in the release
  • Breaking changes - Any breaking changes (for major versions)
  • Migration guide - How to upgrade (if needed)

​
Example Release Notes Structure

## v3.22.0 (2025-01-15)

### Features
- feat(cli): add support for new framework
- feat(web): improve documentation search

### Bug Fixes
- fix(cli): resolve template generation issue
- fix(web): fix mobile navigation

### Chores
- chore: update dependencies
- docs: improve getting started guide

​
Breaking Changes

When a major version is released (e.g., 3.x → 4.x), breaking changes are clearly documented:
  1. What changed - Description of the breaking change
  2. Why it changed - Reasoning behind the change
  3. How to migrate - Step-by-step migration instructions
  4. Code examples - Before/after code samples
Breaking changes only affect the CLI itself. Generated projects are not affected by CLI updates.

​
Contributing to Releases

If you’d like to contribute to Better-T-Stack releases:
  • Report bugs - Open issues for bugs in the current release
  • Suggest features - Propose new features in GitHub Discussions
  • Submit PRs - Contribute code (see Contributing)
  • Test canary builds - Help test pre-release versions

​
Frequently Asked Questions

Release frequency varies based on development activity:
  • Patch releases - As needed for bug fixes (weekly or more)
  • Minor releases - Every 1-2 weeks for new features
  • Major releases - Every few months for breaking changes
Subscribe to releases to stay notified.
No. Once a project is generated, it’s independent of the CLI version. You only need to update if you want to:
  • Use the add command with new addons
  • Generate new projects with latest features
  • Access new CLI commands or options
Your existing projects will continue to work regardless of CLI updates.
Old CLI versions continue to work, but:
  • You won’t have access to new features
  • Bug fixes won’t be available
  • Compatibility with newer dependencies may be limited
  • You may miss security updates
Always use @latest to get the newest version.
Yes. You can use any published version:
npm create better-t-stack@3.20.0
However, this is not recommended unless you have a specific compatibility requirement.
Check these resources:
  • GitHub Issues - Labeled with “enhancement” or “feature request”
  • GitHub Discussions - Community feature discussions
  • Canary releases - Test upcoming features early
  • Pull Requests - See what’s being worked on
  1. Check if it’s already reported in GitHub Issues
  2. If not, open a new issue with:
    • CLI version (create-better-t-stack --version)
    • Steps to reproduce
    • Expected vs actual behavior
    • Error messages (if any)
See Contributing for more details.

​
Additional Resources

GitHub Releases

View all releases and changelogs

Star History

See project growth over time

npm Package

View package on npm registry

Contributing

Learn how to contribute to releases

Build docs developers (and LLMs) love

Get started for freeTalk to us