chore: bump package version to 0.20.0-dev.0

[matthme]

Summary

To ensure that we don't accidentally publish 0.19.x releases from the main branch.

TODO:

• CHANGELOG mentions all code changes.
• docs have been updated (npm run build && git add docs)

Summary by CodeRabbit

• Chores
  • Updated package version to 0.20.0-dev.0 in preparation for upcoming development.

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

[cocogitto-bot]

✔️ 4767132 - Conventional commits check succeeded.

[coderabbitai]

Walkthrough

The package version in package.json was updated from 0.19.0 to 0.20.0-dev.0, marking an interim development release. No other package configuration or logic was modified.

Changes

Cohort / File(s)	Summary
Version Update package.json	Bumped package version from 0.19.0 to 0.20.0-dev.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Straightforward version field modification with no logic or configuration changes

Possibly related PRs

• docs: switch to v0.19 as current #293 — Updates package.json to reference the same ^0.20.0-dev.0 JS client version as a direct dependency change overlap
• chore: release v0.19.0-dev.1 #295 — Modifies package.json version field for release bump purposes
• chore: release 0.19.0 #312 — Changes package.json version field as part of release/version bump workflow

Suggested reviewers

• jost-s
• ThetaSinner

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: bumping the package version to 0.20.0-dev.0, which is the only modification in this changeset.
Description check	✅ Passed	The description includes all required template sections: a Summary explaining the purpose and a TODO checklist matching the template structure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-version-0.20.0-dev.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ccd7f7d and 4767132.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-09-08T05:14:43.481Z

Learnt from: jost-s
Repo: holochain/tryorama PR: 294
File: ts/test/fixture/dna.yaml:2-2
Timestamp: 2025-09-08T05:14:43.481Z
Learning: In Holochain v0.6 upgrades that are in an unfinalized state, manifest_version "0" should be used in dna.yaml and happ.yaml files instead of "1", as confirmed by the project maintainer jost-s in the tryorama repository.

Applied to files:

• package.json

⏰ 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). (2)

• GitHub Check: test (ubuntu-latest)
• GitHub Check: test (macos-latest)

🔇 Additional comments (3)

package.json (3)

4-4: Version format is correct and semver-compliant.

The pre-release version 0.20.0-dev.0 follows semantic versioning correctly and clearly communicates a development interim state, aligning with the PR's intent to prevent accidental 0.19.x releases from main.

---

4-4: Verify that incomplete TODOs do not block merge.

The PR description lists two unchecked TODOs:

• CHANGELOG mentions all code changes
• docs have been updated (npm run build && git add docs)

Clarify whether these must be addressed before merge or are deferred for follow-up.

---

4-4: Review README.md compatibility matrix for version documentation.

The search found version references in documentation that require manual review:

• git/README.md (lines 22-24): Contains version compatibility matrix showing "Tryorama v0.19.x is compatible with JS client v0.20.x" and "Tryorama v0.18.x is compatible with JS client v0.19.x". With package.json now at 0.20.0-dev.0, verify whether this compatibility matrix should be updated to document the new v0.20.x release and its compatible dependencies.

• git/CHANGELOG.md: Contains historical v0.19.0 entries, which should remain unchanged.

No hardcoded 0.19.0 references were found in config files (JSON/YAML/TOML) or CI/CD workflows outside of documentation and changelog.

---

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