mcp-postgresql-ops 3.4.1__tar.gz → 3.4.2__tar.gz

mcp_postgresql_ops-3.4.1/README.md → mcp_postgresql_ops-3.4.2/PKG-INFO

@@ -1,3 +1,21 @@
+Metadata-Version: 2.4
+Name: mcp-postgresql-ops
+Version: 3.4.2
+Summary: Add your description here
+Author-email: JungJungIn <call518@gmail.com>
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: fastmcp>=2.12.3
+Requires-Dist: asyncpg>=0.29.0
+Requires-Dist: psycopg2-binary>=2.9.7
+Requires-Dist: setuptools-scm>=10.0.5
+Requires-Dist: pre-commit>=4.6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
+Dynamic: license-file
+
 # MCP Server for PostgreSQL Operations and Monitoring
 
 [![MCP Toplist](https://mcptoplist.com/badge/smithery%2Fcall518%2Fmcp-postgresql-ops.svg)](https://mcptoplist.com/server/smithery%2Fcall518%2Fmcp-postgresql-ops)
@@ -291,20 +309,6 @@ The `create-test-data.sql` script is executed by the `postgres-init-extensions`
 
 ---
 
-## Tagged Releases
-
-The GitHub Actions workflow publishes a pushed version tag (for example,
-`v1.2.3`, `1.2.3`, or `1.2.3rc1`) to TestPyPI, then PyPI, and finally creates
-a GitHub Release with the tag as its title. Both distribution versions must match
-the tag. The existing `testpypi` and `pypi` GitHub environments must have Trusted
-Publishing configured on their respective package indexes.
-
-Release notes include full commit messages since the most recently published
-GitHub Release, or all commits for the first release. The previous release tag
-must be an ancestor of the new tag. Alpha, beta, and release candidate tags create
-prereleases. Existing published releases are preserved; an existing draft requires
-manual review. A failed publication prevents subsequent publication jobs.
-
 ## Installation
 
 ### From PyPI (Recommended)

mcp_postgresql_ops-3.4.1/src/mcp_postgresql_ops.egg-info/PKG-INFO → mcp_postgresql_ops-3.4.2/README.md

@@ -1,21 +1,3 @@
-Metadata-Version: 2.4
-Name: mcp-postgresql-ops
-Version: 3.4.1
-Summary: Add your description here
-Author-email: JungJungIn <call518@gmail.com>
-Requires-Python: >=3.12
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: fastmcp>=2.12.3
-Requires-Dist: asyncpg>=0.29.0
-Requires-Dist: psycopg2-binary>=2.9.7
-Requires-Dist: setuptools-scm>=10.0.5
-Requires-Dist: pre-commit>=4.6.0
-Provides-Extra: dev
-Requires-Dist: pytest>=7.0.0; extra == "dev"
-Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
-Dynamic: license-file
-
 # MCP Server for PostgreSQL Operations and Monitoring
 
 [![MCP Toplist](https://mcptoplist.com/badge/smithery%2Fcall518%2Fmcp-postgresql-ops.svg)](https://mcptoplist.com/server/smithery%2Fcall518%2Fmcp-postgresql-ops)
@@ -309,20 +291,6 @@ The `create-test-data.sql` script is executed by the `postgres-init-extensions`
 
 ---
 
-## Tagged Releases
-
-The GitHub Actions workflow publishes a pushed version tag (for example,
-`v1.2.3`, `1.2.3`, or `1.2.3rc1`) to TestPyPI, then PyPI, and finally creates
-a GitHub Release with the tag as its title. Both distribution versions must match
-the tag. The existing `testpypi` and `pypi` GitHub environments must have Trusted
-Publishing configured on their respective package indexes.
-
-Release notes include full commit messages since the most recently published
-GitHub Release, or all commits for the first release. The previous release tag
-must be an ancestor of the new tag. Alpha, beta, and release candidate tags create
-prereleases. Existing published releases are preserved; an existing draft requires
-manual review. A failed publication prevents subsequent publication jobs.
-
 ## Installation
 
 ### From PyPI (Recommended)

{mcp_postgresql_ops-3.4.1 → mcp_postgresql_ops-3.4.2}/scripts/check_release.py

@@ -10,13 +10,10 @@ from pathlib import Path
 
 def release_version(tag: str) -> str:
     """Validate a canonical release tag and return its package version."""
-    version = tag.removeprefix("v")
     number = r"(?:0|[1-9][0-9]*)"
-    if not re.fullmatch(
-        rf"{number}\.{number}\.{number}(?:(?:a|b|rc){number})?", version
-    ):
-        raise ValueError("Use a tag such as 0.5.7, v0.5.7, or 0.5.7rc1")
-    return version
+    if not re.fullmatch(rf"{number}\.{number}\.{number}", tag):
+        raise ValueError("Use a numeric major.minor.patch tag such as 0.5.7")
+    return tag
 
 
 def check_release(tag: str, directory: Path) -> None:

{mcp_postgresql_ops-3.4.1 → mcp_postgresql_ops-3.4.2}/scripts/publish_release.py

@@ -69,7 +69,7 @@ def release_notes(repository: str, tag: str, previous: str | None) -> str:
 
 def publish_release(repository: str, tag: str) -> None:
     """Create a release once, using the last published release as the baseline."""
-    version = release_version(tag)
+    release_version(tag)
     current = command("git", "rev-parse", "--verify", f"refs/tags/{tag}^{{commit}}")
     remote = command("gh", "api", f"repos/{repository}/commits/{tag}", "--jq", ".sha")
     if current != remote or current != command("git", "rev-parse", "HEAD"):
@@ -117,8 +117,6 @@ def publish_release(repository: str, tag: str) -> None:
             "--notes-file",
             str(path),
         ]
-        if re.search(r"(?:a|b|rc)\d+$", version):
-            args.extend(["--prerelease", "--latest=false"])
         command(*args)
     print(f"Published GitHub Release {tag} (previous release: {previous or 'none'}).")
 

{mcp_postgresql_ops-3.4.1 → mcp_postgresql_ops-3.4.2/src/mcp_postgresql_ops.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcp-postgresql-ops
-Version: 3.4.1
+Version: 3.4.2
 Summary: Add your description here
 Author-email: JungJungIn <call518@gmail.com>
 Requires-Python: >=3.12
@@ -309,20 +309,6 @@ The `create-test-data.sql` script is executed by the `postgres-init-extensions`
 
 ---
 
-## Tagged Releases
-
-The GitHub Actions workflow publishes a pushed version tag (for example,
-`v1.2.3`, `1.2.3`, or `1.2.3rc1`) to TestPyPI, then PyPI, and finally creates
-a GitHub Release with the tag as its title. Both distribution versions must match
-the tag. The existing `testpypi` and `pypi` GitHub environments must have Trusted
-Publishing configured on their respective package indexes.
-
-Release notes include full commit messages since the most recently published
-GitHub Release, or all commits for the first release. The previous release tag
-must be an ancestor of the new tag. Alpha, beta, and release candidate tags create
-prereleases. Existing published releases are preserved; an existing draft requires
-manual review. A failed publication prevents subsequent publication jobs.
-
 ## Installation
 
 ### From PyPI (Recommended)

{mcp_postgresql_ops-3.4.1 → mcp_postgresql_ops-3.4.2}/src/mcp_postgresql_ops.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "3.4.1",
+  "tag": "3.4.2",
   "distance": 0,
-  "node": "g040ffedb6a319f1cd3ceec18f5ec489bac8a41e1",
+  "node": "g0b8e72718a54b7db8b4997f0828e4498c3366eae",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-10-24"

{mcp_postgresql_ops-3.4.1 → mcp_postgresql_ops-3.4.2}/tests/test_release.py

@@ -16,12 +16,18 @@ from scripts.check_release import check_release, release_version
 from scripts.publish_release import publish_release, release_notes
 
 
-@pytest.mark.parametrize("tag", ["1.2.3", "v1.2.3", "1.2.3rc1"])
+@pytest.mark.parametrize("tag", ["0.0.0", "1.2.3", "10.20.30"])
 def test_release_version(tag):
-    assert release_version(tag) == tag.removeprefix("v")
+    assert release_version(tag) == tag
 
 
-@pytest.mark.parametrize("tag", ["latest", "1.2", "v01.2.3", "1.2.3+local"])
+@pytest.mark.parametrize(
+    "tag",
+    [
+        "latest", "1.2", "1.2.3.4", "v1.2.3", "01.2.3", "1.02.3", "1.2.03",
+        "1.2.3a1", "1.2.3b1", "1.2.3rc1", "1.2.3+local", "1..3", "１.2.3",
+    ],
+)
 def test_invalid_release_version(tag):
     with pytest.raises(ValueError):
         release_version(tag)
@@ -37,20 +43,20 @@ def test_distribution_versions(tmp_path, version):
         info.size = len(metadata)
         archive.addfile(info, io.BytesIO(metadata))
     if version == "1.2.3":
-        check_release("v1.2.3", tmp_path)
+        check_release("1.2.3", tmp_path)
     else:
         with pytest.raises(ValueError, match="expected"):
-            check_release("v1.2.3", tmp_path)
+            check_release("1.2.3", tmp_path)
 
 
 def test_notes_use_previous_release_and_preserve_messages():
     message = "Fix issue\n\n```\n$(touch unwanted)\n```"
     with patch("scripts.publish_release.command") as command:
         command.side_effect = ["new", "old", "", f"abcdef123\0{message}\0"]
-        notes = release_notes("owner/repo", "v1.2.3", "v1.2.2")
+        notes = release_notes("owner/repo", "1.2.3", "1.2.2")
     assert message in notes
     assert "````text" in notes
-    assert "compare/v1.2.2...v1.2.3" in notes
+    assert "compare/1.2.2...1.2.3" in notes
     assert command.call_args.args[-2:] == ("old..new", "--")
 
 
@@ -59,28 +65,38 @@ def test_existing_release_is_not_overwritten(draft):
     with patch("scripts.publish_release.command") as command:
         command.side_effect = [
             "sha", "sha", "sha",
-            json.dumps([[{"tag_name": "v1.2.3", "draft": draft}]]),
+            json.dumps([[{"tag_name": "1.2.3", "draft": draft}]]),
         ]
         if draft:
             with pytest.raises(ValueError, match="draft"):
-                publish_release("owner/repo", "v1.2.3")
+                publish_release("owner/repo", "1.2.3")
         else:
-            publish_release("owner/repo", "v1.2.3")
+            publish_release("owner/repo", "1.2.3")
     assert command.call_count == 4
 
 
-def test_first_prerelease_creation():
+def test_first_release_creation():
     with patch("scripts.publish_release.command") as command:
         command.side_effect = ["sha", "sha", "sha", "[[]]", "sha", "", ""]
-        publish_release("owner/repo", "v1.2.3rc1")
+        publish_release("owner/repo", "1.2.3")
     args = command.call_args.args
     assert args[:3] == ("gh", "release", "create")
-    assert args[-2:] == ("--prerelease", "--latest=false")
+    assert args[3] == "1.2.3"
+    assert "--prerelease" not in args
+    assert "--latest=false" not in args
 
 
 def test_remote_tag_mismatch_stops_publication():
     with patch("scripts.publish_release.command") as command:
         command.side_effect = ["local", "remote"]
         with pytest.raises(ValueError, match="must match"):
-            publish_release("owner/repo", "v1.2.3")
+            publish_release("owner/repo", "1.2.3")
     assert command.call_count == 2
+
+
+@pytest.mark.parametrize("tag", ["v1.2.3", "1.2.3rc1"])
+def test_invalid_tag_stops_publication(tag):
+    with patch("scripts.publish_release.command") as command:
+        with pytest.raises(ValueError):
+            publish_release("owner/repo", tag)
+    command.assert_not_called()