@@ -4,7 +4,7 @@ This repository uses [Changesets](https://github.com/changesets/changesets) to m
44
55## Package Versioning Strategy
66
7- - ** SDK** (` @plotday/sdk ` ): Independent versioning
7+ - ** SDK** (` @plotday/agent ` ): Independent versioning
88- ** Tools** (` @plotday/tool-* ` ): Independent versioning
99- ** Agents** (` @plotday/agent-* ` ): Not published, excluded from releases
1010
@@ -102,7 +102,7 @@ This tagging convention allows you to:
102102
103103Each GitHub release includes:
104104
105- - ** Title** : Package name and version (e.g., ` @plotday/sdk @0.9.1 ` )
105+ - ** Title** : Package name and version (e.g., ` @plotday/agent @0.9.1 ` )
106106- ** Release Notes** : Automatically extracted from the package's CHANGELOG.md for that version
107107- ** Assets** : None (packages are distributed via npm)
108108
@@ -121,7 +121,7 @@ If you need to create a GitHub release manually after publishing:
121121
122122``` bash
123123# For SDK
124- gh release create sdk@0.9.1 --title " @plotday/sdk @0.9.1" --notes " Release notes here"
124+ gh release create sdk@0.9.1 --title " @plotday/agent @0.9.1" --notes " Release notes here"
125125
126126# For a tool
127127gh release create tool-google-calendar@0.1.0 --title " @plotday/tool-google-calendar@0.1.0" --notes " Release notes here"
@@ -198,7 +198,7 @@ git push
198198pnpm release
199199
200200# 5. (Optional) Create GitHub release manually
201- gh release create sdk@0.9.1 --title " @plotday/sdk @0.9.1" --notes " Release notes"
201+ gh release create sdk@0.9.1 --title " @plotday/agent @0.9.1" --notes " Release notes"
202202```
203203
204204⚠️ This should only be done in emergencies. The automated workflow is preferred.
0 commit comments