You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3.**Fix versions before committing**: Restore master's marketplace name (`maister-plugins`) and set the new release version (not beta version) in all three manifest files
77
+
4.**Commit the feature**: `git commit -m "Feature description"`
78
+
5.**Bump version**: Separate commit for the version bump
7.**Set beta version**: Update manifests to next beta version (e.g., `X.Y.Z-beta.1`) with marketplace name `maister-plugins-beta`, commit
81
+
8.**Push both**: `git push origin master beta`
82
+
83
+
### Why reset beta after squash?
84
+
85
+
After `git merge --squash`, git doesn't record that beta's commits were merged. A regular `git merge master` back to beta would try to replay all old commits, causing conflicts. `reset --hard master` is safe because all beta work is preserved on master.
86
+
87
+
### Manifest files to update
88
+
89
+
These three files need version/name changes during the merge workflow:
90
+
-`.claude-plugin/marketplace.json` — name + version + descriptions
91
+
-`plugins/maister/.claude-plugin/plugin.json` — version + description
92
+
-`plugins/maister-copilot/.claude-plugin/plugin.json` — version + description
0 commit comments