common-python-tasks 0.5.0__tar.gz → 0.5.1__tar.gz

{common_python_tasks-0.5.0 → common_python_tasks-0.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: common-python-tasks
-Version: 0.5.0
+Version: 0.5.1
 Summary: Opinionated Poe the Poet tasks for Python package development.
 Project-URL: Homepage, http://github.com/ci-sourcerer/common-python-tasks
 Project-URL: Source, http://github.com/ci-sourcerer/common-python-tasks.git
@@ -55,7 +55,7 @@ To install a specific release, set the environment variable `COMMON_PYTHON_TASKS
 curl -sSL https://api.github.com/repos/ci-sourcerer/common-python-tasks/contents/scripts/add_common_python_tasks.py \
   | jq -r '.content' \
   | base64 -d \
-  | COMMON_PYTHON_TASKS_VERSION=0.5.0 python3
+  | COMMON_PYTHON_TASKS_VERSION=0.5.1 python3
 ```
 
 This will complete the following steps.
@@ -75,7 +75,7 @@ There's no real reason to run the automated script; I just like automating every
     ```toml
     [project]
     dependencies = [
-        "common-python-tasks==0.5.0"  # Always pin to a specific version
+        "common-python-tasks==0.5.1"  # Always pin to a specific version
     ]
 
     [tool.poe]
@@ -309,8 +309,8 @@ By default, `tasks()` exposes the common task set. You can still include or excl
 ```toml
 [project]
 name = "simple-cli-tool"
-version = "0.5.0"
-dependencies = ["common-python-tasks==0.5.0"]
+version = "0.5.1"
+dependencies = ["common-python-tasks==0.5.1"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks()"
@@ -322,7 +322,7 @@ Available tasks: common defaults such as `format`, `lint`, `test`, and `build`.
 
 ```toml
 [project]
-dependencies = ["common-python-tasks==0.5.0"]
+dependencies = ["common-python-tasks==0.5.1"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks(include_tags=['common', 'containers'])"
@@ -338,7 +338,7 @@ Available tasks: All tasks including `build-image` and `push-image`.
 
 ```toml
 [project]
-dependencies = ["common-python-tasks==0.5.0"]
+dependencies = ["common-python-tasks==0.5.1"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks()"

{common_python_tasks-0.5.0 → common_python_tasks-0.5.1}/README.md

@@ -20,7 +20,7 @@ To install a specific release, set the environment variable `COMMON_PYTHON_TASKS
 curl -sSL https://api.github.com/repos/ci-sourcerer/common-python-tasks/contents/scripts/add_common_python_tasks.py \
   | jq -r '.content' \
   | base64 -d \
-  | COMMON_PYTHON_TASKS_VERSION=0.5.0 python3
+  | COMMON_PYTHON_TASKS_VERSION=0.5.1 python3
 ```
 
 This will complete the following steps.
@@ -40,7 +40,7 @@ There's no real reason to run the automated script; I just like automating every
     ```toml
     [project]
     dependencies = [
-        "common-python-tasks==0.5.0"  # Always pin to a specific version
+        "common-python-tasks==0.5.1"  # Always pin to a specific version
     ]
 
     [tool.poe]
@@ -274,8 +274,8 @@ By default, `tasks()` exposes the common task set. You can still include or excl
 ```toml
 [project]
 name = "simple-cli-tool"
-version = "0.5.0"
-dependencies = ["common-python-tasks==0.5.0"]
+version = "0.5.1"
+dependencies = ["common-python-tasks==0.5.1"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks()"
@@ -287,7 +287,7 @@ Available tasks: common defaults such as `format`, `lint`, `test`, and `build`.
 
 ```toml
 [project]
-dependencies = ["common-python-tasks==0.5.0"]
+dependencies = ["common-python-tasks==0.5.1"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks(include_tags=['common', 'containers'])"
@@ -303,7 +303,7 @@ Available tasks: All tasks including `build-image` and `push-image`.
 
 ```toml
 [project]
-dependencies = ["common-python-tasks==0.5.0"]
+dependencies = ["common-python-tasks==0.5.1"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks()"

{common_python_tasks-0.5.0 → common_python_tasks-0.5.1}/src/common_python_tasks/github.py

@@ -475,7 +475,8 @@ def get_github_release_asset_paths(
         asset_sources: Optional list of paths or glob patterns. When a string is
             provided (including via `GITHUB_RELEASE_ASSETS`), values are
             interpreted as colon-separated paths or glob patterns.
-            If not provided, the default value is `dist/*`.
+            If not provided, the default value is `dist/*`. An empty list
+            explicitly disables asset selection.
 
     Returns:
         A sorted list of existing asset paths.
@@ -513,7 +514,7 @@ def get_github_release_asset_paths(
         elif path.exists():
             LOGGER.warning("Ignoring non-file GitHub release asset path: %s", path)
 
-    if not asset_paths and explicit_assets:
+    if not asset_paths and explicit_assets and source_items:
         utils.fatal(
             "No GitHub Release assets were found for the configured asset paths: "
             + ":".join(source_items)

{common_python_tasks-0.5.0 → common_python_tasks-0.5.1}/src/common_python_tasks/tasks.py

@@ -1000,7 +1000,8 @@ def publish_github_release(
         release_name or os.getenv("GITHUB_RELEASE_NAME") or resolved_tag_name
     )
     resolved_body = body or os.getenv("GITHUB_RELEASE_BODY")
-    asset_paths = get_github_release_asset_paths(assets)
+    # Poe supplies `[]` when an optional repeated CLI argument is omitted.
+    asset_paths = get_github_release_asset_paths(assets or None)
 
     return publish_github_release_helper(
         resolved_tag_name,