mainsequence 9.0.5__tar.gz → 9.0.6.dev36__tar.gz

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

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

{mainsequence-9.0.5 → mainsequence-9.0.6.dev36}/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

{mainsequence-9.0.5 → mainsequence-9.0.6.dev36}/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 → mainsequence-9.0.6.dev36}/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 → mainsequence-9.0.6.dev36/mainsequence.egg-info}/PKG-INFO

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

{mainsequence-9.0.5 → mainsequence-9.0.6.dev36}/pyproject.toml

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