[VPDPersonal]

Why. The Asset Store product moves to the UPM Publisher Portal, so buyers get a real package from My Assets, and the old .unitypackage upload path no longer applies.

What

• SETUP.md: install from My Assets into Packages, samples from the Samples tab
• asp-ft-release: upload through the UPM portal and UPM Publishing Tools
• A stable release PR merges only after the store publishes the version
• Release checklist follows the new upload and order
• Dev project drops the embedded com.unity.asset-store-tools

Start with: .claude/skills/asp-ft-release/SKILL.md (section "Asset Store upload"), then Aspid.FastTools/Packages/tech.aspid.fasttools/SETUP.md

Verification

• node scripts/check-package-files.mjs, check-unity-minimum.mjs, check-skills.mjs → pass
• Headless Unity 6000.6.5f1, a project with only com.unity.upm-publishing-tools 0.3.3 → resolves with the account's entitlement and compiles, no error CS
• git grep 'asset-store-tools\|ASTOOLS' → only the skill's "do not use" note

Context

The upload runs from the head of chore/release-<version> while the release PR is open: a merge switches the READMEs and the site to #upm before the tag publishes upm. com.unity.upm-publishing-tools stays out of the dev manifest, because it resolves only for an account that has it in My Assets. The README, Welcome window and site link to the old store page (slug/365584) and say that a git URL install next to the store copy gives two copies; both change in a separate PR after the store publishes product 2333465.

🤖 Generated with Claude Code

[claude]

Verdict: 1 blocking, 3 minor
Holding the stable tag until the store publishes leaves the stable README, badge and site on main pointing at a #upm ref and a release that do not exist for the whole review.

[VPDPersonal]

@claude review the commits after your last review

[claude]

Claude finished @VPDPersonal's task in 1m 8s —— View job

---

I reviewed bf543ac and 82c8ba5: no blocking issues, 3 minor

• Read the two commits after the last review
• Checked whether the 4 earlier findings are fixed
• Posted inline comments and the verdict comment

Earlier findings: all 4 are fixed.

• The upload now runs from the open release PR, and the PR merges only after the store publishes.
• A rejected version is closed without a merge.
• The checklist is split into §11 and §12.
• com.unity.upm-publishing-tools and its lock entries are out of the dev project.

New findings (inline):

1. SKILL.md:151 Hold scope: the package's CHANGELOG.md is generated from the root CHANGELOG.md.
   • The hold blocks only PRs that change the package folder. A docs-only PR merged during the review can put a note under [X.Y.Z], and then upm/X.Y.Z lists a change that the uploaded package does not have.
   • The date edit after approval also makes the published CHANGELOG.md differ from the uploaded copy.
2. SKILL.md:178 Reusing the version after a rejection: the rerun of Phase 1 breaks.
   • git switch -c fails if the old local branch exists, and the push collides with the closed PR's remote branch.
   • gh pr view <branch> can then find the closed PR.
   • Delete the old branch first.
3. SKILL.md:78-79 Merged too early: Phase 2 stops with no way to recover. Offer two choices: tag now, or revert the release commit until the store publishes.

The verdict comment is posted. I changed no files.

[claude]

Verdict: 0 blocking, 3 minor
bf543ac and 82c8ba5 resolve all four earlier findings. The new findings concern the hold scope (the root CHANGELOG feeds the package), a rerun of a rejected version with the same number, and recovery from an early merge.