Skip to content

fix: bump skill.json version to 2.6.2#382

Merged
mrgoonie merged 2 commits into
nextlevelbuilder:mainfrom
shipengqi:fix/bump-skill-json-version-2.6.2
Jun 24, 2026
Merged

fix: bump skill.json version to 2.6.2#382
mrgoonie merged 2 commits into
nextlevelbuilder:mainfrom
shipengqi:fix/bump-skill-json-version-2.6.2

Conversation

@shipengqi

Copy link
Copy Markdown
Contributor

Summary

  • Bumps skill.json version from 2.5.0 to 2.6.2 to match the latest GitHub release

Why

The latest release tag is v2.6.2 (released 2026-06-22), but skill.json still declares version 2.5.0. This causes claude plugins update to report "already at latest version (2.5.0)" even though a newer version exists — the Claude Code plugin system reads skill.json to determine the available version.

Related release: https://github.com/nextlevelbuilder/ui-ux-pro-max-skill/releases/tag/v2.6.2

@mrgoonie mrgoonie left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary: This PR is a narrow metadata version bump so Claude plugin/package metadata matches the latest GitHub release v2.6.2. The diff is limited to the three version fields that currently remain at 2.5.0 on main.

Risk level: Low

Mandatory gates:

  • Duplicate/prior implementation: clear — searched open/closed PRs and issues for 2.6.2, skill.json version, and the plugin update symptom; only this open PR targets the current v2.6.2 mismatch. Older issue #202 was the same class of problem for a previous release.
  • Project standards: passed — the PR updates plugin/marketplace/root metadata only and does not touch generated skill assets or source data.
  • Strategic necessity: clear value — keeping skill.json / Claude plugin metadata aligned with the published release prevents plugin update flows from reporting the stale 2.5.0 version.
  • CI/checks: missing/not required — no status checks are reported, but the change is JSON-only metadata and was validated against the published v2.6.2 GitHub release.

Findings:

  • Critical: none.
  • Important: none.
  • Suggestion: consider making the release automation added in #375 update these metadata version fields during the release process so future tags do not leave plugin metadata stale.

Verdict: APPROVE

Posted by /github-maintain at 2026-06-24T02:58:00Z

@mrgoonie mrgoonie merged commit a13b2a0 into nextlevelbuilder:main Jun 24, 2026
@mrgoonie mrgoonie added agent:github-maintain Processed by github-maintain automation pr:reviewed PR reviewed by maintain workflow pr:approved-by-maintain Approved by github-maintain workflow pr:merge-ready PR is merge-ready by maintain workflow pr:merged-by-maintain Merged by github-maintain workflow labels Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent:github-maintain Processed by github-maintain automation pr:approved-by-maintain Approved by github-maintain workflow pr:merge-ready PR is merge-ready by maintain workflow pr:merged-by-maintain Merged by github-maintain workflow pr:reviewed PR reviewed by maintain workflow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants