dailybot-cli 1.0.1__tar.gz → 1.2.0__tar.gz

{dailybot_cli-1.0.1 → dailybot_cli-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dailybot-cli
-Version: 1.0.1
+Version: 1.2.0
 Summary: Dailybot CLI - The command-line bridge between humans and agents. Progress reports, observability, and workflow automation for modern teams across Slack, Google Chat, Discord, MS Teams, and more.
 Author-email: Dailybot <support@dailybot.com>
 License: MIT
@@ -36,7 +36,7 @@ Dynamic: license-file
 
 The command-line bridge between **humans** and **agents**. [Dailybot](https://www.dailybot.com) connects your team — whether they work in Slack, Google Chat, Discord, Microsoft Teams, or the web — with AI agents and automated workflows. The CLI brings that power to your terminal: progress reports, observability, health checks, messaging, and workflow automation for modern teams.
 
-## Installation
+## Installation.
 
 ```bash
 pip install dailybot-cli

{dailybot_cli-1.0.1 → dailybot_cli-1.2.0}/README.md

@@ -2,7 +2,7 @@
 
 The command-line bridge between **humans** and **agents**. [Dailybot](https://www.dailybot.com) connects your team — whether they work in Slack, Google Chat, Discord, Microsoft Teams, or the web — with AI agents and automated workflows. The CLI brings that power to your terminal: progress reports, observability, health checks, messaging, and workflow automation for modern teams.
 
-## Installation
+## Installation.
 
 ```bash
 pip install dailybot-cli

{dailybot_cli-1.0.1 → dailybot_cli-1.2.0}/dailybot_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dailybot-cli
-Version: 1.0.1
+Version: 1.2.0
 Summary: Dailybot CLI - The command-line bridge between humans and agents. Progress reports, observability, and workflow automation for modern teams across Slack, Google Chat, Discord, MS Teams, and more.
 Author-email: Dailybot <support@dailybot.com>
 License: MIT
@@ -36,7 +36,7 @@ Dynamic: license-file
 
 The command-line bridge between **humans** and **agents**. [Dailybot](https://www.dailybot.com) connects your team — whether they work in Slack, Google Chat, Discord, Microsoft Teams, or the web — with AI agents and automated workflows. The CLI brings that power to your terminal: progress reports, observability, health checks, messaging, and workflow automation for modern teams.
 
-## Installation
+## Installation.
 
 ```bash
 pip install dailybot-cli

{dailybot_cli-1.0.1 → dailybot_cli-1.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "dailybot-cli"
-version = "1.0.1"
+version = "1.2.0"
 description = "Dailybot CLI - The command-line bridge between humans and agents. Progress reports, observability, and workflow automation for modern teams across Slack, Google Chat, Discord, MS Teams, and more."
 readme = "README.md"
 license = {text = "MIT"}
@@ -156,6 +156,19 @@ version_toml = ["pyproject.toml:project.version"]
 branch = "main"
 tag_format = "v{version}"
 commit_message = "chore(release): {version}\n\n[skip ci]"
+# Author + tagger of the auto-generated `chore(release)` commit and the v* tag.
+# Without this, PSR defaults to "semantic-release <semantic-release>", which
+# obscures who actually owns the automation. We use a branded identity that
+# matches the bot account holding AUTOMATION_GITHUB_TOKEN.
+#
+# IMPORTANT: for the commit to show the `dailybotops` avatar + profile link
+# in the GitHub UI, the email below must be a verified secondary email on
+# the `dailybotops` GitHub account
+# (https://github.com/settings/emails → Add email address). Without that
+# verification, GitHub renders the commit author as a plain "DailyBot
+# Automations" string (no avatar, no profile link). The commit identity is
+# still valid in git itself either way.
+commit_author = "DailyBot Automations <ops@dailybot.com>"
 build_command = ""                 # release.yml owns the actual build/upload
 # `allow_zero_version` and `major_on_zero` together control how PSR treats
 # breaking changes while the package is still on 0.x.
@@ -184,7 +197,14 @@ allowed_tags = [
 ]
 minor_tags = ["feat"]
 patch_tags = ["fix", "perf"]
-default_bump_level = 0  # 0 = no release when no releasable commits exist
+# Every merge to main produces a release, period. Devs do not need to remember
+# conventional-commit prefixes — if they forget, the merge still ships as a
+# PATCH bump. If they DO follow the convention, they unlock finer control:
+#   feat:                          → MINOR (1.0.1 → 1.1.0)
+#   fix: / perf:                   → PATCH (1.0.1 → 1.0.2)
+#   feat!: or BREAKING CHANGE:     → MAJOR (1.0.1 → 2.0.0)
+#   anything else (chore/docs/...) → PATCH (default_bump_level = 1)
+default_bump_level = 1
 
 [tool.semantic_release.changelog]
 exclude_commit_patterns = [