chore: bump version to 1.1.0

[harshtandiya]

Cuts the 1.1.0 release from main, covering everything backported since v1.0.0.

This also writes down the branch policy we're adopting: main carries the 1.x stable line, develop carries the 2.x beta line. Team-based multi-tenancy (#312 / #317) is v2 material and stays on develop.

Changes

• buzz/__init__.py: __version__ → 1.1.0 (the version of record; pyproject.toml reads it dynamically)
• package.json: version → 1.1.0 for consistency — note the 1.0.0 release only touched buzz/__init__.py, so drop this hunk if you'd rather keep the bump to a single file
• New CHANGELOG.md, seeded with this release and a 1.0.0 baseline entry

dashboard/package.json is left at 0.0.0 — it has never been bumped and isn't published.

Release contents

13 commits on main since v1.0.0:

Breaking — the dashboard was migrated to frappe-ui v1 and Vite 8 (#283). Component imports, prop names and build output changed with the frappe-ui major, so the dashboard needs a rebuild and downstream customisations are affected. No Python API or DocType schema change, so no data migration.

Added — Zoom-backed events (#292), Buzz workspace dashboard (#314), speaker-editable talk proposals (#276), short timezone label on Buzz Event (#282), End Date autofill (#316)

Changed — buzz/api split into typed domain packages (#307), PhoneInput for phone fields (#290), README hero (#285)

Fixed — confirm before accepting a proposal (#309), prefill "To" on proposal emails (#294), semgrep full-repo findings (#281)

CI — merge-queue trigger gaps (#279)

Versioning note

#283 is a feat!, which strict semver would make a 2.0.0. It's shipping as a minor deliberately: the break is dashboard-internal, and 2.0.0 is reserved for the v2 line on develop. The breaking change is called out prominently in the changelog instead.

Do not backport this one

Unlike the 1.0.0 bump (#270 → #271), this must not get a backport develop label — develop should carry a 2.0.0-beta version, not 1.1.0. Happy to open that bump as a separate PR against develop.

After merge

Tag v1.1.0 on the merge commit on main and publish the release. Worth noting the v1.0.0 tag points at 13a1a29, the develop-side backport commit rather than main's 85fa5f6 — tagging this one on main keeps the line consistent going forward.

---

Generated by Claude Code

[greptile-apps]

Greptile Summary

This PR prepares the 1.1.0 stable release by synchronizing Python and root package metadata and adding release history and branch-policy documentation.

• Bumps the authoritative Python package version to 1.1.0.
• Aligns the root JavaScript package metadata with the release.
• Adds a changelog covering 1.0.0, 1.1.0, release-line policy, and the dashboard breaking change.

Confidence Score: 4/5

The PR appears safe to merge, with only a non-blocking ambiguity in the documented dashboard rebuild command.

The Python and root package versions are consistently updated and do not conflict with repository build metadata; the remaining concern is that administrators running the release instructions from a bench root must infer the Buzz app directory before yarn build will work.

Files Needing Attention: CHANGELOG.md

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds comprehensive release notes and branch policy, but the dashboard rebuild command should identify the directory from which it must be run.
buzz/init.py	Correctly updates the sole authoritative dynamic Python package version to 1.1.0.
package.json	Keeps root package metadata aligned with the Python release version without requiring a lockfile update.

Prompt To Fix All With AI

### Issue 1
CHANGELOG.md:23
**Build command lacks location**
The unqualified `yarn build` command is only exposed from the Buzz repository root. Administrators following these upgrade instructions from a Frappe bench root receive a command failure and must infer the correct directory before rebuilding the dashboard assets.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore: bump version to 1.1.0" | Re-trigger Greptile}

[greptile-apps]

Build command lacks location

The unqualified yarn build command is only exposed from the Buzz repository root. Administrators following these upgrade instructions from a Frappe bench root receive a command failure and must infer the correct directory before rebuilding the dashboard assets.

Prompt To Fix With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 23
Comment:
**Build command lacks location**
The unqualified `yarn build` command is only exposed from the Buzz repository root. Administrators following these upgrade instructions from a Frappe bench root receive a command failure and must infer the correct directory before rebuilding the dashboard assets.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!