4 Commits
Author SHA1 Message Date
Andrés Zsögön 9305ca6a7a Release 1.1.2 with refreshed versioned Registry previews
Replace the Registry animation with consistently aligned node screenshots, retain the Inuyasha and Ayame showcase, and publish it as banner_112.gif for cache-safe delivery.
2026-07-20 17:57:49 -03:00
Andrés Zsögön 9a8f689fae Release 1.1.1 with animated Registry banner 2026-07-20 10:52:30 -03:00
Andrés Zsögön b1cb565255 Stop tracking Python cache files 2026-07-03 12:17:27 -03:00
Andrés Zsögön a4ed0d9f09 Document release tag descriptions 2026-07-03 11:53:36 -03:00
6 changed files with 4 additions and 1 deletions
+2
View File
@@ -24,6 +24,8 @@ Operational Rules for AI Coding Agents
## Version Tagging
- When a commit bumps the version in `pyproject.toml`, create and push the matching Git tag targeting that exact commit before doing anything else.
- The version-bump commit must have a user-facing release message that summarizes the actual changes in that version. Do not use a generic subject such as `Bump version to 1.0.7` by itself. Use a descriptive subject such as `Prepare 1.0.7 release with user-defined style indicators`.
- New version tags must include a concise description of the changes shipped in that version. Create release tags as annotated tags with a title like `Release 1.0.7` and bullet-point notes summarizing the user-visible changes and important fixes. Users should be able to understand what changed from the tag page alone.
- The tag name must exactly match the version string in `pyproject.toml` (e.g., `1.0.0`, `1.0.1`, `1.2.3`). **No `v` prefix, no other format.** This repo uses plain numeric tags only (e.g., `1.2.0`, never `v1.2.0`).
- Before creating a release tag, inspect the existing tags in the repo (`git tag --list`) to confirm the naming convention in use. For this repo the required format is always plain numeric (e.g., `1.2.0`).
- The README version badge (`shields.io github/v/tag`) may render the tag with a `v` prefix (e.g., display `v1.2.0`) even when the actual Git tag is `1.2.0`. This is normal shields.io display behaviour — do **not** create a `v`-prefixed tag to match the badge display.
Binary file not shown.

After

Width:  |  Height:  |  Size: 2.6 MiB

Binary file not shown.
Binary file not shown.
+2 -1
View File
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
[project]
name = "comfyui-lora-pipeline"
version = "1.1.0"
version = "1.1.2"
description = "Area-based LoRA scheduling and area conditioning wrappers for ComfyUI."
readme = "README.md"
requires-python = ">=3.10"
@@ -20,3 +20,4 @@ Documentation = "https://github.com/andreszs/comfyui-lora-pipeline#readme"
PublisherId = "andreszs"
DisplayName = "LoRA Pipeline"
Icon = ""
Banner = "https://raw.githubusercontent.com/andreszs/comfyui-lora-pipeline/refs/heads/main/assets/banner_112.gif"