ace-git 0.19.0 → 0.19.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 20769f2cd0637983959bf770812eb746d5334f8b22a5466f8c4398b5a9a9a54a
-  data.tar.gz: 6225bf184de1971c3f180f23353938e9f4d48acd44f99438cfe1eeb53421d9c4
+  metadata.gz: f1f4338a90a1289acd437a01c2ef439d3020123e9d915ed22c3eff4f8ec63055
+  data.tar.gz: 75fefab777b61d2abe6a1e5b5abf0692c19bf7fbec58d527bf12c536314c22a7
 SHA512:
-  metadata.gz: 5d707e9c9fedc65363f7fd8a9e9e8513e04b1978fc4b2b7fb7a4d1244ac0a59bcff4f9dd73f4de0e8261622d5ab253b73c7be194d2df0820ab0635701282e39b
-  data.tar.gz: 930bf870b7b7e4cd7b86081cec6ef8766356dfb2b8e91273b93e29fe7398ffe38343bf390b204de9172ccb655523747307d6bf854a78a3c609d5cf0e8a6686f4
+  metadata.gz: 81b8365e99bcb4b7026aa9d4b5eefe6e1e4a2d1f07f0e48ebdc2fc06eb1a2bc95425c5ac69f911b2342f01045da159f4bd4676bc8a918ad4bba2a09078c838f0
+  data.tar.gz: c2fb0f10917ff79992b517a6a7e74be8bf09fff4eecf343ca33e55e74a2a20be20f3700f7f170326c6eb5e8b421b87d5ee1539ec6b9e9153853fd29cbc03d67d

data/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.19.2] - 2026-03-29
+
+### Technical
+- Normalized published gem metadata so RubyGems and Ruby Toolbox use current release information instead of the 1980 fallback date.
+
+## [0.19.1] - 2026-03-29
+
+### Fixed
+- Added an explicit `git push` step to `github/release-publish` after changelog finalization so release target commits exist on GitHub before `gh release create`.
+
+### Technical
+- Added a stop-and-recover rule for GitHub API validation errors caused by local-only target commits (`tag_name is not a valid tag`, `target_commitish is invalid`) so the workflow pushes before retrying release creation.
+
 ## [0.19.0] - 2026-03-29
 
 ### Changed

data/handbook/workflow-instructions/github/release-publish.wf.md

@@ -84,7 +84,13 @@ If `[Unreleased]` has content:
    ace-git-commit CHANGELOG.md -i "finalize changelog v0.9.933 from unreleased"
    ```
 
-4. Proceed to step 2 with the newly created versioned entry available for publishing.
+4. **Push the finalization commit before creating releases:**
+   ```bash
+   git push
+   ```
+   The release target commit must exist on GitHub before `gh release create` can tag and publish it.
+
+5. Proceed to step 2 with the newly created versioned entry available for publishing.
 
 ### 2. Parse Root CHANGELOG
 
@@ -119,6 +125,15 @@ Use `$group_by` to choose the release body layout. Release tags/titles still use
 - `package` (default): within each date bucket, group entries as package blocks and then categories.
 - `date`: preserve legacy behavior, one release body per date in descending version order separated by `---`.
 
+Mixed-release presentation rule:
+
+- If a date bucket contains one or more clear primary changes plus follower packages that exist only because of
+  dependency-constraint propagation, render the primary package sections first.
+- Collapse follower-only dependency fallout into one compact trailing `### Technical side effects` section instead
+  of expanding every follower into a full package block.
+- Keep follower packages explicit by name/version, but prefer a short list over repeated full prose when the
+  release value is driven elsewhere.
+
 Date mode example:
 
 ```markdown
@@ -164,6 +179,8 @@ Package-mode parse rules:
 - Track the most recent package version seen for each package in the date bucket for package headers.
 - Render categories in `fixed,added,changed,technical` unless `$category_order` overrides.
 - If a bullet does not match the package pattern, place it under a fallback package section `### 📦 other`.
+- If `### Technical` contains a compact follower summary list, preserve it as a single trailing `### Technical side effects`
+  section rather than exploding it back into per-package blocks.
 
 ### 5. Resolve Target Commits
 
@@ -190,6 +207,12 @@ If no commit is found for a version group, skip it and report:
 
 Process each daily group from oldest date to newest:
 
+Before each live release creation:
+
+- Verify the chosen `${SHA}` exists on the remote branch you intend to tag.
+- If the workflow created or committed the changelog entry locally during step 1.5, ensure that commit has already been pushed before continuing.
+- If `gh release create` reports `tag_name is not a valid tag` or `target_commitish is invalid`, stop and push the missing commit instead of retrying the same release command unchanged.
+
 **Dry-run mode** (`--dry-run`):
 
 ```text

data/lib/ace/git/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Git
-    VERSION = '0.19.0'
+    VERSION = '0.19.2'
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ace-git
 version: !ruby/object:Gem::Version
-  version: 0.19.0
+  version: 0.19.2
 platform: ruby
 authors:
 - Michal Czyz
 bindir: exe
 cert_chain: []
-date: 1980-01-02 00:00:00.000000000 Z
+date: 2026-03-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ace-support-config
@@ -180,7 +180,7 @@ licenses:
 metadata:
   allowed_push_host: https://rubygems.org
   homepage_uri: https://github.com/cs3b/ace/tree/main/ace-git
-  source_code_uri: https://github.com/cs3b/ace
+  source_code_uri: https://github.com/cs3b/ace/tree/main/ace-git/
   changelog_uri: https://github.com/cs3b/ace/blob/main/ace-git/CHANGELOG.md
 rdoc_options: []
 require_paths: