Closes #1065

Overview

This PR introduces a new GitHub Actions workflow: continuous-release.yml.
The workflow runs on:

• Pushes to the default branch (aka merges to main)
• Pull request events

It automatically builds and publishes packages to pkg.pr.new's registry.

For pull requests, pkg.pr.new comments with installation URLs for packages, and updates the comments with every new commit.

Example pkg.pr.new PR comment:

In the absence of pull requests, you can access package URLs by manually constructing them using this format:

https://pkg.pr.new/reatom/reatom/@reatom/<package-name>@<commit-hash>

Or browse published packages at: https://pkg.pr.new/~/reatom/reatom

Motivation

Reatom packages are typically released in batches. This workflow introduces a "continuous release" strategy by leveraging pkg.pr.new, which allows:

• Sharing experimental builds immediately
• Publishing hotfixes without waiting for a full release cycle

How It Works

Setup

In order to use pkg.pr.new, you must install the pkg.pr.new GitHub application on the repository: https://github.com/apps/pkg-pr-new

Features

• Triggering: PR events and pushes to default branch
• Concurrency: Cancels in-progress runs on new commits to the same PR
• Environment:
  • OS: ubuntu-latest
  • Node.js: 22.13.1
  • pnpm: 10.12.1
• Steps:
  • Checkout code
  • Set up Node.js and pnpm
  • Install dependencies via pnpm install
  • Build packages using Turbo
  • Publish packages via pnpm dlx pkg-pr-new

More Notes

Question: Should the push trigger be removed from the workflow? Since all changes are merged through pull requests, and those PRs already trigger the workflow, it may be redundant to run it again on pushing to main.

Notes & Considerations

• No Node.js caching: Skipped due to missing lockfile
• Versioning: Follows versions used in lint.yml, test.yml, and package.json
• StackBlitz preview: Disabled as it's not relevant for package publishing

Optional Enhancements

• Add a pkg.pr.new badge to the README
• Conditionally publish only if lint/tests pass
  (Note: skipped for now, as tests may be outdated, and we want to allow previews even if they fail)
• Use Turbo caching to cut build times further
  (requires setting up credentials/secrets)
• Optimize by only building and publishing changed packages (reduces time by ~50% or ~40s per run, but additional scripting may make it less maintainable):

set -euo pipefail
# Get packages changed vs upstream base and include dependents
npx turbo run build --filter=...[upstream/${{ github.base_ref }}...HEAD] --dry=json \
  | jq -r '.tasks[].directory' \
  | sort -u > changed-dirs.txt

if [ ! -s changed-dirs.txt ]; then
  echo "paths=" >> "$GITHUB_OUTPUT"
  echo "No changed packages."
else
  CHANGED_PATHS=$(sed -e 's|^|./|' changed-dirs.txt | xargs)
  echo "paths=$CHANGED_PATHS" >> "$GITHUB_OUTPUT"
  echo "Changed paths: $CHANGED_PATHS"
fi