app-interface.csv shows newer repo/release state version 2.5.0, but npm still ships older version 2.2.3

[ia-abatista]

Hey guys, when running the 'uipro init --ai codex' or even 'uipro update' the previous version skills are installed and not the new version.

[ia-abatista]

I submitted a fix, please review and approve is appropriate: #355

Not sure if @Spinulosa1111 addressed these in his unpublished fixes

[Spinulosa1111]

Hi @ia-abatista — yes, this is exactly what the unpublished fixes address. The root cause is that the repo has never had an automated release pipeline, so npm has been stuck on 2.2.3 while the repo moved to 2.5.0.

PR #348 includes a GitHub Actions release workflow that:

• Resolves symlinks before packaging (fixing the install failures too)
• Builds and publishes a clean ZIP + checksums.sha256 automatically when a version tag is pushed
• Bumps the npm package to match the repo version

Once @nextlevelbuilder merges the queued PRs and tags v2.5.1, the workflow will publish automatically and this gap will be closed for good.

Your PR #355 may overlap with some of this — @nextlevelbuilder should review both together to avoid duplication. Happy to coordinate if needed!

[ia-abatista]

Thanks for responding @Spinulosa1111 - I really hope @nextlevelbuilder responds soon, the repo has been stale for several months now, would be a shame to abandon it. The community should probably consider forking or hopefully others can get additional access to help manage it.

[Ray0907]

Hi @ia-abatista @Spinulosa1111, I’m one of the contributors here, but I’m not a maintainer and I don’t have merge or release access to this repository.

Since upstream has been quiet for a while and this issue affects the published CLI/package flow, I’ve started a clearly labeled community-maintained fork here:

https://github.com/Ray0907/ui-ux-pro-max-skill

The goal is not to replace the original project or present the fork as official. It is just to keep fixes, releases, and package updates moving while maintainer access is unavailable. If @nextlevelbuilder resumes maintenance or grants access, I’m happy to help upstream the changes and move work back here.

I’ll keep the original attribution and MIT license intact, and any community build will use a separate package name so it does not conflict with the official uipro-cli package.

The first areas I’d like to focus on are the issues already discussed here:

• npm/release version mismatch
• CLI asset sync
• install packaging / symlink issues
• release workflow

Happy to coordinate with anyone working on related PRs so we avoid duplicating effort.

[mrgoonie]

Summary: This is accepted as a real release/package distribution gap, not a source-code support gap. The repo currently declares CLI version 2.5.0, while user installs are still receiving older 2.2.3 behavior.nnDecision: accepted / release pipeline gapnnEvidence:n- The issue reports uipro init --ai codex and uipro update installing previous-version skills.n- cli/package.json in the current repo declares 2.5.0.n- Related PRs/issues already point at the same release path: #348 adds a release workflow, #355 covers CLI asset sync, and #362 confirms npm/CLI packaging can deliver only part of the skill set.n- The maintainer-critical blocker is publishing/release automation, not adding another platform preset.nnNext step: resolve this through one focused release path: get asset sync/package contents correct, merge a working release workflow, then publish/tag a new package so npm users receive the current repo assets. Until that happens, install/update reports against npm should be treated as stale-package symptoms.