ace-git 0.18.5 → 0.19.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1c027540195a5081320ef9e440582480cd4b3682190e40c24d123b4a54dd41f9
-  data.tar.gz: a2ae2188b33cb9762a9436c335da45903d8342f4531dd0a56a19522637bc3e81
+  metadata.gz: f1f4338a90a1289acd437a01c2ef439d3020123e9d915ed22c3eff4f8ec63055
+  data.tar.gz: 75fefab777b61d2abe6a1e5b5abf0692c19bf7fbec58d527bf12c536314c22a7
 SHA512:
-  metadata.gz: a87fcd62b3731fdd3061621431b70ba3cb68c63fa17e8f353ddeef68f84dd603beb9e39e9a9d360a33e73b4160bd73097224995fcb8a4984372eca83751c3d17
-  data.tar.gz: 73e2fc197ad8772004f7244e483434d1555e73cca95641a472900f007fc94a87ad9a044f294785e15003797915925d20e894842b70bc4f75bce2de2c89048392
+  metadata.gz: 81b8365e99bcb4b7026aa9d4b5eefe6e1e4a2d1f07f0e48ebdc2fc06eb1a2bc95425c5ac69f911b2342f01045da159f4bd4676bc8a918ad4bba2a09078c838f0
+  data.tar.gz: c2fb0f10917ff79992b517a6a7e74be8bf09fff4eecf343ca33e55e74a2a20be20f3700f7f170326c6eb5e8b421b87d5ee1539ec6b9e9153853fd29cbc03d67d

data/CHANGELOG.md

@@ -7,6 +7,25 @@ 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
+- Defaulted `github/release-publish` to package-grouped release notes, with `--group-by date` now opting into the legacy layout.
+- Switched live GitHub release creation guidance to `--notes-file` so markdown release bodies with inline code do not break shell execution.
+
 ## [0.18.5] - 2026-03-29
 
 ### Added

data/handbook/skills/as-github-release-publish/SKILL.md

@@ -56,5 +56,6 @@ None
 - Run `ace-bundle wfi://github/release-publish` in the current project to load the workflow instructions.
 - Read the loaded workflow and execute it end-to-end in this project.
 - Follow the workflow as the source of truth.
+- Unless the caller explicitly passes `--group-by date`, treat release body grouping as `package` by default.
 - Do the work described by the workflow instead of only summarizing it.
 - When the workflow requires edits, tests, or commits, perform them in this project.

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

@@ -18,7 +18,7 @@ Create GitHub releases from root `CHANGELOG.md` entries that have no correspondi
 - `$version`: explicit version like `v0.9.846`, or range like `v0.9.840..v0.9.846`
 - `$since`: time filter like `"3 days"` or `"this week"`
 - `$dry_run`: if set, print what would be created without creating anything
-- `$group_by`: optional mode switch. `date` (default) keeps legacy daily grouping. `package` enables package-first grouping inside each date bucket.
+- `$group_by`: optional mode switch. `package` (default) enables package-first grouping inside each date bucket. `date` keeps the legacy daily grouping.
 - `$category_order`: optional ordered category list, e.g. `fixed,added,changed,technical` (defaults to fixed → added → changed → technical)
 
 ## Instructions
@@ -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
 
@@ -116,8 +122,17 @@ No unpublished versions found matching the given criteria.
 
 Use `$group_by` to choose the release body layout. Release tags/titles still use date-bucket grouping (highest version per date).
 
-- `date` (default): preserve current behavior, one release body per date in descending version order separated by `---`.
-- `package`: within each date bucket, group entries as package blocks and then categories.
+- `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:
 
@@ -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
@@ -205,7 +228,7 @@ Process each daily group from oldest date to newest:
 ```bash
 gh release create "v${VERSION}" \
   --title "v${VERSION}" \
-  --notes "${COMBINED_BODY}" \
+  --notes-file ".ace-local/github-release/v${VERSION}-notes.md" \
   --target "${SHA}"
 ```
 

data/lib/ace/git/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Git
-    VERSION = '0.18.5'
+    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.18.5
+  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: