chore: release 0.19.0

[matthme]

Summary

Release 0.19.0

TODO:

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

Summary by CodeRabbit

• New Features
  • Added optional label field for Conductor instances to override default log prefix identification.
  • Introduced integratedOpsCount method to poll and verify integrated operation counts match expected values for specified DNA hashes.

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

[cocogitto-bot]

✔️ a0da6d7 - Conventional commits check succeeded.

[coderabbitai]

Walkthrough

Release of v0.19.0 with version bump and dependency update. Changelog documents two new features: an optional label field for Conductor-related types to override default log-prefix labels, and an integratedOpsCount method for polling integrated ops verification.

Changes

Cohort / File(s)	Summary
Release and version documentation CHANGELOG.md, package.json	Version bumped from 0.19.0-dev.2 to 0.19.0; @holochain/client dependency updated from ^0.20.0-dev.2 to ^0.20.0. Changelog updated with Unreleased section scaffolding and v0.19.0 release notes documenting optional label field for AppWithOptions, ConductorOptions, CreateConductorOptions, and addConductor, plus new integratedOpsCount polling method.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Simple version and dependency updates with no logic changes
• Straightforward changelog documentation of new features

Possibly related PRs

• docs: switch to v0.19 as current #293 — Updates @holochain/client dependency in package.json, same dependency field affected by this PR

Suggested reviewers

• jost-s
• ThetaSinner

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: release 0.19.0' clearly and concisely summarizes the main purpose of the pull request—to release version 0.19.0.
Description check	✅ Passed	The description includes the required Summary and TODO sections from the template. However, the second TODO item about updating docs remains incomplete.
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 0.19.0

---

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: 1

🧹 Nitpick comments (1)

CHANGELOG.md (1)

1-26: Verify that docs have been regenerated and committed per PR objectives.

The PR objectives mention a TODO checklist that requires docs to be updated (instruction: npm run build && git add docs). This review only shows package.json and CHANGELOG.md, but does not include the generated docs/ folder. Please confirm that:

1. You've run npm run build to regenerate the API documentation
2. The resulting docs/ folder changes have been committed to this PR

The build script (line 29 in package.json) runs tsc && npm run build:docs, which generates the TypeScript types and API docs. Skipping this step would leave the documentation out of sync with the code changes.

Would you like me to generate a verification script to check if the docs folder has been updated and committed in this PR?

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7d795c and a0da6d7.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• package.json (2 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:

• CHANGELOG.md
• 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 (macos-latest)
• GitHub Check: test (ubuntu-latest)

🔇 Additional comments (3)

package.json (1)

4-4: Version bump to stable release looks good.

The version correctly transitions from pre-release (0.19.0-dev.2) to stable (0.19.0).

CHANGELOG.md (2)

5-10: Unreleased section structure is good.

The new Unreleased section with standard subsections (Added/Removed/Changed/Fixed) follows Keep a Changelog best practices.

---

12-26: Release notes are comprehensive and well-documented.

The v0.19.0 release entry includes all code changes across Added/Removed/Changed/Fixed sections with proper PR references (#302, #303, #305). The BREAKING change for conductorCellsDhtSync removal is clearly marked. Format is consistent with the project's changelog conventions and Semantic Versioning.