Skip to content

internal: Add beta changesets release #2000

internal: Add beta changesets release

internal: Add beta changesets release #2000

Triggered via push October 6, 2025 02:32
Status Failure
Total duration 36s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Release
could not parse changeset - invalid frontmatter: # Beta Release Guide This project now supports beta releases using changesets. Here's how to use it: ## Automatic Beta Releases Beta releases are automatically triggered when: 1. Changes are pushed to the `beta` branch 2. The workflow is manually triggered via GitHub Actions ## Manual Beta Release You can manually trigger a beta release by: 1. Go to the GitHub Actions tab 2. Select "Beta Release" workflow 3. Click "Run workflow" 4. Choose the beta tag (default: `beta`) 5. Click "Run workflow" ## Beta Release Process 1. **Versioning**: Uses `changeset version --snapshot beta` to create beta versions 2. **Publishing**: Publishes packages with the `beta` tag to npm 3. **Version Format**: Beta versions follow the pattern `{version}-beta-{datetime}-{commit}` ## Installing Beta Packages Users can install beta versions using: ```bash npm install @data-client/react@beta # or yarn add @data-client/react@beta ``` ## Creating Changesets for Beta To create a changeset for beta release: ```bash yarn changeset ``` Then select the packages and changes you want to include in the beta release. ## Local Beta Testing To test beta releases locally: ```bash # Create beta version yarn changeset:version:beta # Build and publish locally (for testing) yarn changeset:publish:beta ``` ## Notes - Beta releases are published with the `beta` tag on npm - The workflow creates a pull request for version bumps - Beta versions are automatically calculated with timestamps and commit hashes - All linked packages are versioned together
Release
Error: could not parse changeset - invalid frontmatter: # Beta Release Guide This project now supports beta releases using changesets. Here's how to use it: ## Automatic Beta Releases Beta releases are automatically triggered when: 1. Changes are pushed to the `beta` branch 2. The workflow is manually triggered via GitHub Actions ## Manual Beta Release You can manually trigger a beta release by: 1. Go to the GitHub Actions tab 2. Select "Beta Release" workflow 3. Click "Run workflow" 4. Choose the beta tag (default: `beta`) 5. Click "Run workflow" ## Beta Release Process 1. **Versioning**: Uses `changeset version --snapshot beta` to create beta versions 2. **Publishing**: Publishes packages with the `beta` tag to npm 3. **Version Format**: Beta versions follow the pattern `{version}-beta-{datetime}-{commit}` ## Installing Beta Packages Users can install beta versions using: ```bash npm install @data-client/react@beta # or yarn add @data-client/react@beta ``` ## Creating Changesets for Beta To create a changeset for beta release: ```bash yarn changeset ``` Then select the packages and changes you want to include in the beta release. ## Local Beta Testing To test beta releases locally: ```bash # Create beta version yarn changeset:version:beta # Build and publish locally (for testing) yarn changeset:publish:beta ``` ## Notes - Beta releases are published with the `beta` tag on npm - The workflow creates a pull request for version bumps - Beta versions are automatically calculated with timestamps and commit hashes - All linked packages are versioned together