[devfive-relay-c70423]

The release retry after #85 still executed the old archive paths. Changepacks Action checks out the merge commit of the latest merged Update Versions PR before running its publish commands. For this release that is #84's commit a85c58a, whose configuration predates #85. Fixing the configuration on main alone therefore cannot repair that frozen release source.

Add a patch changepack for the same three packages from #83. The next version update will create a new release source that includes #85's corrected publish configuration. Existing release tags remain unchanged. Fetch becomes 0.1.27, generator 0.1.29, utils 0.1.15, and eight dependents receive their automatic patch updates.

After this PR merges, merge the generated Update Versions PR to publish from the new release source. PR CI success alone does not confirm npm publication.

Validation:

• Confirmed the failed run used main 314de83, while its selected release source a85c58a still contains the old commands.
• Changepacks 0.3.6 check reports the expected 11-package version update.
• Ran the actual changepacks update --yes in an isolated clone; verified all expected versions and preservation of the corrected configuration.
• Using CI's Bun 1.4.4, ran the actual changepacks publish --dry-run against all 11 updated targets with the normal online npm checks; every target passed. No npm publication was performed.
• Inspected all 11 generated archives: expected package names and versions, no unresolved workspace dependencies.

Failed run: https://github.com/dev-five-git/devup-api/actions/runs/41951294647

---

Submitted via Devfive hub.
Employee Git identity (self-declared): <>
Device: 3099154426bffbeef8b62999b80bb038

[github-actions]

Changepacks

@devup-api/fetch@0.1.26 → 0.1.27 - packages/fetch/package.json

Patch

• Retry the nullable-ref and server-action fixes from a new release commit containing the corrected package-local publish archive paths; the previous release attempt failed before registry publication

@devup-api/generator@0.1.28 → 0.1.29 - packages/generator/package.json

Patch

• Retry the nullable-ref and server-action fixes from a new release commit containing the corrected package-local publish archive paths; the previous release attempt failed before registry publication

@devup-api/hookform@0.1.10 → 0.1.11 - packages/hookform/package.json

Patch

• Auto-update: depends on '@devup-api/fetch' via a local workspace dependency

@devup-api/next-plugin@0.1.17 → 0.1.18 - packages/next-plugin/package.json

Patch

• Auto-update: depends on '@devup-api/generator' via a local workspace dependency

@devup-api/react-query@0.1.20 → 0.1.21 - packages/react-query/package.json

Patch

• Auto-update: depends on '@devup-api/fetch' via a local workspace dependency

@devup-api/rsbuild-plugin@0.1.17 → 0.1.18 - packages/rsbuild-plugin/package.json

Patch

• Auto-update: depends on '@devup-api/generator' via a local workspace dependency

@devup-api/ui@0.1.7 → 0.1.8 - packages/ui/package.json

Patch

• Auto-update: depends on '@devup-api/hookform' via a local workspace dependency

@devup-api/utils@0.1.14 → 0.1.15 - packages/utils/package.json

Patch

• Retry the nullable-ref and server-action fixes from a new release commit containing the corrected package-local publish archive paths; the previous release attempt failed before registry publication

@devup-api/vite-plugin@0.1.17 → 0.1.18 - packages/vite-plugin/package.json

Patch

• Auto-update: depends on '@devup-api/generator' via a local workspace dependency

@devup-api/webpack-plugin@0.1.17 → 0.1.18 - packages/webpack-plugin/package.json

Patch

• Auto-update: depends on '@devup-api/generator' via a local workspace dependency

@devup-api/zod@0.1.8 → 0.1.9 - packages/zod/package.json

Patch

• Auto-update: depends on '@devup-api/fetch' via a local workspace dependency