mainsequence 9.0.5.dev35__tar.gz → 9.0.6.dev37__tar.gz

{mainsequence-9.0.5.dev35/mainsequence.egg-info → mainsequence-9.0.6.dev37}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 9.0.5.dev35
+Version: 9.0.6.dev37
 Summary: Main Sequence SDK
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

{mainsequence-9.0.5.dev35 → mainsequence-9.0.6.dev37}/agent_scaffold/skills/maintenance/code_repository_maintenance/SKILL.md

@@ -248,8 +248,8 @@ The platform deploys from the push according to the repository's
 pushes deploy:
 
 - omitted or `null`: every push to the branch deploys;
-- a regular expression: a push deploys only when a matching tag points at the
-  branch's latest commit.
+- a regular expression: a matching tag deploys the commit it points at, whether
+  that is the branch's latest commit or an older commit on the branch.
 
 Automatic deployment and `tag_regex` are set in the workflow file only; a
 `ResourceRelease` or `Job` update does not accept them. The Main Sequence
@@ -300,6 +300,85 @@ only the commits CI tagged. Details:
 Do not call `sync-after-commit` or any backend repair endpoint. The GitHub
 branch-push webhook owns backend repository reconciliation.
 
+### Development Deploys Every Push, Production Deploys Tags
+
+A common setup uses two workflow files scoped to Environments. On the
+production branch only the first applies; on the development branch only the
+second:
+
+```yaml
+# .mainsequence/workflows/api-production.yaml
+api_version: "2.3.0"
+name: api-production
+scope:
+  environments: [production]
+resources:
+  - key: api
+    kind: fastapi
+    spec:
+      source_path: api/main.py
+      automatic_deployment: true
+      automatic_redeployment:
+        enabled: true
+        tag_regex: "^v[0-9]+\\.[0-9]+\\.[0-9]+$"
+```
+
+```yaml
+# .mainsequence/workflows/api-development.yaml
+api_version: "2.3.0"
+name: api-development
+scope:
+  environments: [development]  # the development Environment's exact name
+resources:
+  - key: api
+    kind: fastapi
+    spec:
+      source_path: api/main.py
+      automatic_deployment: true
+      automatic_redeployment:
+        enabled: true
+```
+
+A push to the development branch deploys at once. A merge to `main` deploys
+nothing until a matching tag points at a commit on `main`; with the release job
+above, CI creates that tag after the tests pass. Take the exact fields from the
+branch's workflow template and validate each file through the branch's
+`validate-workflow` action before committing it, as the
+`platform_operations/orchestration_and_releases` skill describes.
+
+### Creating A Release Tag
+
+The platform reacts to the tag push, however the tag was made. The short tag
+name must fully match `tag_regex`, and the tagged commit must be on the
+target's branch (its latest commit or an older one).
+
+- CI, as in the release job above. This is the recommended path.
+- By hand, only when the user asks for it:
+
+  ```bash
+  git tag v1.3.0 <commit>
+  git push origin v1.3.0
+  ```
+
+  Lightweight and annotated tags both work. Push one tag at a time: GitHub
+  sends no event when more than three tags are pushed at once, so
+  `git push --tags` can deploy nothing.
+- A GitHub Release: publishing a release with a new tag, in the web UI or with
+  `gh release create v1.3.0 --target main`, creates the tag, and that tag
+  deploys like a pushed one.
+
+A tag created with the Actions `GITHUB_TOKEN` starts no other GitHub Actions
+workflow, but it still reaches Main Sequence. Deleting a tag deploys nothing
+and removes nothing. A tag that does not match, or whose commit is only on
+another branch, deploys nothing for that target.
+
+### Going Back To An Older Version
+
+Revert the change and release a new version: `git revert <commit>`, raise the
+patch version with `uv version --bump patch`, commit, push, and let CI tag the
+result. The version keeps moving forward and every deployed commit matches its
+tag.
+
 ## Diagnose Partial Completion Before Retrying
 
 Never rerun an entire mutating workflow blindly.

{mainsequence-9.0.5.dev35 → mainsequence-9.0.6.dev37}/agent_scaffold/skills/platform_operations/orchestration_and_releases/SKILL.md

@@ -224,7 +224,7 @@ Automatic deployment and its `tag_regex` are set in the repository's `.mainseque
 The declaration's `tag_regex` decides which pushes deploy:
 
 - omitted or `null`: every push to the branch deploys
-- a regular expression: a push deploys only when a matching tag points at the branch's latest commit
+- a regular expression: a matching tag deploys the commit it points at, whether that is the branch's latest commit or an older commit on the branch
 
 The platform does not create or name tags. Release tags come from the repository's own CI, for example a GitHub Actions workflow that tags the version declared in `pyproject.toml` after the tests pass. The maintenance skill `.agents/skills/mainsequence/maintenance/code_repository_maintenance/SKILL.md` has an example. `mainsequence code-repository sync` only refreshes `uv.lock`, the local environment, and `requirements.txt`; it does not commit, tag, or push.
 

{mainsequence-9.0.5.dev35 → mainsequence-9.0.6.dev37}/mainsequence/client/models_helpers.py

@@ -107,8 +107,8 @@ class AutomaticRedeploymentPolicy(BaseModel):
         description=(
             "Regular expression matched against repository tags, set by `tag_regex` "
             "in the repository's `.mainsequence/workflows/*.yaml`. Null deploys every "
-            "push; a regex deploys only when a matching tag points at the branch's "
-            "latest commit."
+            "push; a regex deploys the commit a matching tag points at, whether it is "
+            "the branch's latest commit or an older commit on the branch."
         ),
         examples=[None, r"^v(?:0|[1-9][0-9]*)\.(?:0|[1-9][0-9]*)\.(?:0|[1-9][0-9]*)$"],
     )

{mainsequence-9.0.5.dev35 → mainsequence-9.0.6.dev37/mainsequence.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 9.0.5.dev35
+Version: 9.0.6.dev37
 Summary: Main Sequence SDK
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

{mainsequence-9.0.5.dev35 → mainsequence-9.0.6.dev37}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mainsequence"
-version = "9.0.5.dev35"
+version = "9.0.6.dev37"
 description = "Main Sequence SDK"
 readme = "README.md"
 requires-python = ">=3.13"