prepare for next beta release

[aspiers]

Summary by CodeRabbit

• Chores
  • Updated SDK version to 0.10.0-beta.0.
  • Improved release process for multi-package versioning workflow.
  • Updated version tracking and release commit messaging to support multiple packages.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0371b2b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

Adjusts versioning strategy and release pipeline to support multi-package versioning. Updates .changeset/pre.json and package version fields from 0.9.0 and 1.0.0-beta.0 respectively to 0.10.0-beta.0, and modifies the GitHub Actions release workflow to handle per-package version tracking instead of single-root versioning.

Changes

Cohort / File(s)	Summary
Changeset Configuration .changeset/migrate-to-lexicon-package.md, .changeset/pre.json	Adjusts scheduled release bump severity from major to minor; updates initial versions for two packages from 0.9.0 to 0.10.0
Release Workflow .github/workflows/release.yml	Replaces single-root version handling with multi-package versioning; beta commit and publish steps now loop over packages/*/package.json to gather names and versions, building consolidated version summaries for commit messages and logs
Package Version packages/sdk-core/package.json	Updates version field from "1.0.0-beta.0" to "0.10.0-beta.0"

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Hopping through versions, we align our way,
From single roots to packages at play,
0.10.0 beta hops into sight,
Multi-package releases, now shining bright! ✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'prepare for next beta release' directly aligns with the PR's main objective of preparing the codebase for the next beta release by updating versions, changesets, and release workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dbbfac5 and 0371b2b.

📒 Files selected for processing (4)

• .changeset/migrate-to-lexicon-package.md
• .changeset/pre.json
• .github/workflows/release.yml
• packages/sdk-core/package.json

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: CR
Repo: hypercerts-org/hypercerts-sdk PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-06T17:56:38.894Z
Learning: Use Changesets for versioning with flow: feature → develop (beta) → main (stable), with beta publishes from develop and stable publishes from main

📚 Learning: 2026-01-06T17:56:38.894Z

Learnt from: CR
Repo: hypercerts-org/hypercerts-sdk PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-06T17:56:38.894Z
Learning: Applies to **/*.{ts,tsx} : Use the error hierarchy from sdk-core/src/core/errors.ts with base HypercertsError and specific error classes (ValidationError, AuthenticationError, NetworkError, NotFoundError, SDSRequiredError)

Applied to files:

• .changeset/migrate-to-lexicon-package.md

📚 Learning: 2026-01-06T17:56:38.894Z

Learnt from: CR
Repo: hypercerts-org/hypercerts-sdk PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-06T17:56:38.894Z
Learning: The SDK should follow a package hierarchy with sdk-react depending on sdk-core, and both packages exporting multiple entrypoints for different purposes

Applied to files:

• .changeset/migrate-to-lexicon-package.md

📚 Learning: 2026-01-06T17:56:38.894Z

Learnt from: CR
Repo: hypercerts-org/hypercerts-sdk PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-06T17:56:38.894Z
Learning: Use Changesets for versioning with flow: feature → develop (beta) → main (stable), with beta publishes from develop and stable publishes from main

Applied to files:

• .github/workflows/release.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Upload results

🔇 Additional comments (5)

.changeset/pre.json (1)

5-6: LGTM! Version bump is consistent.

The minor version increment from 0.9.0 to 0.10.0 for both packages is appropriate for the beta release preparation and aligns with the coordinated versioning strategy.

.github/workflows/release.yml (2)

105-117: LGTM! Multi-package version tracking is correctly implemented.

The workflow now properly loops through all packages to collect version information and includes it in both the commit message body and logs. The use of echo -e to interpret newlines ensures proper formatting.

---

165-170: LGTM! Logging correctly reflects multi-package beta releases.

The logging step properly iterates through packages and displays individual package versions, consistent with the commit message format.

.changeset/migrate-to-lexicon-package.md (1)

2-2: LGTM! Minor bump is appropriate for 0.x versioning strategy.

The change from major to minor bump is consistent with the shift to the 0.x version series (0.10.0-beta.0). In the 0.x series, breaking changes are conventionally acceptable in minor releases, as the package is still considered pre-1.0 and under active development.

Note: The changeset documents several breaking changes (lines 19-30), which would normally require a major bump in 1.x+ versions, but the 0.x convention allows for this flexibility.

packages/sdk-core/package.json (1)

3-3: No action required. The version 0.10.0-beta.0 is the latest in a forward progression of beta releases (0.2.0 → 0.4.0 → 0.5.0 → 0.6.0 → 0.7.0 → 0.8.0 → 0.9.0 → 0.10.0-beta.0). There is no 1.0.0-beta.0 version published on npm, so no downgrade has occurred. The versioning strategy has been consistent throughout the 0.x beta series.

Likely an incorrect or invalid review comment.

---

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.}

[Copilot]

Pull request overview

This PR prepares the repository for the next beta release by correcting version numbers and updating the release workflow to support a monorepo structure with multiple packages.

• Downgrades sdk-core version from 1.0.0-beta.0 to 0.10.0-beta.0 to align with the intended version sequence
• Updates changeset configuration to reflect the new initial versions (0.10.0) and changes sdk-core release type from major to minor
• Enhances the GitHub Actions release workflow to iterate over all packages in the monorepo rather than reading a single root package.json

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
packages/sdk-core/package.json	Downgrades version from 1.0.0-beta.0 to 0.10.0-beta.0
.changeset/pre.json	Updates initial versions from 0.9.0 to 0.10.0 for both sdk-core and sdk-react packages
.changeset/migrate-to-lexicon-package.md	Changes sdk-core release type from major to minor to align with semantic versioning for 0.x releases
.github/workflows/release.yml	Updates beta release workflow to loop through all packages instead of reading a single package.json file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The version is being downgraded from 1.0.0-beta.0 to 0.10.0-beta.0. If version 1.0.0-beta.0 has already been published to npm, this downgrade will cause issues as npm does not allow publishing a lower version after a higher version has been published. Consider using a version like 1.0.1-beta.0 instead, or if the package hasn't been published yet, ensure any tags or releases for 1.0.0-beta.0 are removed.

Suggested change

	"version": "0.10.0-beta.0",
	"version": "1.0.1-beta.0",