Alpha

[favorodera]

Summary by CodeRabbit

• Chores
  • Version bumped to 1.0.0-alpha.1
  • Release workflow and publishing process revamped (branch filters, concurrency, permissions, install/publish steps)
  • Pre-release configuration added for alpha channel and initial pre-release sequencing
  • Changeset added to record a patch release note and workflow-related versioning
  • Release scripts moved to CI-specific commands and reorganized

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds pre-release config for zod-sqlite, updates the GitHub Actions release workflow to invoke Changesets CLI directly, and bumps package.json to 1.0.0-alpha.1 while replacing a public release script with CI-specific scripts.

Changes

Cohort / File(s)	Summary
Pre-release Configuration \.changeset/pre.json	New file enabling pre-release mode with tag alpha, initial version 1.0.0-alpha.1 for zod-sqlite, and an empty changesets array.
Changeset Entry \.changeset/giant-feet-glow.md	New changeset noting a patch release for zod-sqlite with the note "Fix workflows".
Release Workflow \.github/workflows/release.yml	Workflow updated: removed beta branch filter, added concurrency, changed permissions to id-token: write, renamed/adjusted steps (checkout, pnpm, node, install), removed legacy dist-tag logic and registry-url, and now runs pnpm dlx @changesets/cli publish.
Package Manifest package.json	Version bumped 0.1.0-alpha.3 → 1.0.0-alpha.1; removed public release script; added ci:release (pnpm build && pnpm dlx @changesets/cli publish) and ci:version (pnpm dlx @changesets/cli version && pnpm install --no-frozen-lockfile).

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant GH as GitHub Actions
  participant Runner as Runner
  participant Repo as Repository (code)
  participant Changesets as Changesets CLI
  participant Registry as npm Registry

  rect rgba(135,206,235,0.12)
    note right of GH: Release workflow triggered
  end

  GH->>Runner: Start job
  Runner->>Repo: Checkout (fetch-depth: 0)
  Runner->>Runner: Setup Node (v24) & Setup pnpm
  Runner->>Repo: Install dependencies (pnpm install --frozen-lockfile)
  Runner->>Changesets: Run `pnpm dlx `@changesets/cli` publish`
  Changesets->>Registry: Authenticate (NPM_TOKEN via env)
  Changesets->>Registry: Publish packages (pre-release tag: alpha)
  Registry-->>Changesets: Confirm publish
  Changesets-->>GH: Return publish result
  GH->>GH: Conclude job (concurrency enforced)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Alpha #1: Makes the same edits to .changeset/pre.json, .github/workflows/release.yml, and package.json to enable pre-release flow and switch to Changesets CLI-based publishing.

Poem

🐰 Alpha hops with tiny feet,

Changesets guide each CI beat,
Scripts refreshed and tags set right,
Pre-release dawns, a soft delight,
Versioned paths leap into light ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Alpha' is vague and generic, failing to convey specific information about the changeset despite multiple substantial modifications.	Use a more descriptive title that captures the main change, such as 'Configure release workflow and pre-release setup' or 'Set up alpha pre-release configuration and CI/CD pipeline'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d27d68 and d7ec804.

📒 Files selected for processing (1)

• .changeset/giant-feet-glow.md

✅ Files skipped from review due to trivial changes (1)

• .changeset/giant-feet-glow.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

package.json (1)

51-52: Consider workflow alignment with ci:release script.

The ci:release script includes an explicit build step before publishing, but the workflow in .github/workflows/release.yml calls pnpm dlx @changesets/cli publish directly rather than using pnpm run ci:release. While the build will still execute via the prepublishOnly hook, this indirection could cause confusion. Consider either:

1. Update the workflow to use pnpm run ci:release for clarity
2. Document that the workflow relies on prepublishOnly for building

The ci:version script correctly uses --no-frozen-lockfile to allow lockfile updates during version bumps.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6c8481d and 6d27d68.

📒 Files selected for processing (3)

• .changeset/pre.json
• .github/workflows/release.yml
• package.json

🔇 Additional comments (7)

.changeset/pre.json (1)

1-8: LGTM! Pre-release configuration is correct.

The Changesets pre-release configuration is properly structured with the alpha tag and initial version matching package.json (1.0.0-alpha.1). The empty changesets array is expected when initializing pre-release mode.

package.json (1)

3-3: Verify the major version bump is intentional.

The version has jumped from 0.1.0-alpha.3 to 1.0.0-alpha.1, which represents a major version change. Please confirm this aligns with your release strategy and whether there are breaking changes that warrant this bump.

.github/workflows/release.yml (5)

8-8: Good addition of concurrency control.

The concurrency setting prevents multiple release workflows from running simultaneously on the same branch, which is essential for avoiding race conditions during version bumps and publishing.

---

13-13: Permission change aligns with NPM provenance.

The change from packages: write to id-token: write suggests you're using NPM's provenance feature for enhanced supply chain security. This is a recommended practice for modern package publishing.

---

19-22: LGTM! Correct checkout configuration for Changesets.

Setting fetch-depth: 0 ensures the full git history is available, which is necessary for Changesets to properly determine version bumps and generate changelogs.

---

24-36: LGTM! Setup steps are well-configured.

The setup steps correctly configure pnpm and Node.js with appropriate versions and caching. Using --frozen-lockfile ensures reproducible builds. The removal of registry-url from Node setup is appropriate when using id-token: write for provenance-based publishing.

---

38-45: Workflow relies on prepublishOnly hook for building.

The publish step directly calls pnpm dlx @changesets/cli publish without an explicit build step. The build will execute via the prepublishOnly hook in package.json. While functional, this was noted in the package.json review as potentially confusing.