/ui5-version
Optional UI5 version to query (e.g., 1.120.0, 1.108, latest). Defaults to project version.
$ npx -y skills add secondsky/sap-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ui5-version
Context preview
What this command does when you run it.
Optional UI5 version to query (e.g., 1.120.0, 1.108, latest). Defaults to project version.
Command definition
ui5-version.mdname: ui5-version
description: Display UI5 version information, support status, release notes, and upgrade paths
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "[version]"
arguments:
- name: version
description: Optional UI5 version to query (e.g., 1.120.0, 1.108, latest). Defaults to project version.
required: falseShell Snippet Notes
- Shell snippets assume Bash on Linux/macOS, WSL2, or Git Bash.
- Install the command-specific tooling shown near each snippet before running it.
- Confirm before running commands that delete files, change ownership, deploy, or modify remote systems.
Output Contract
Return detected or requested UI5 version details, support status, upgrade notes, local evidence, and unresolved package/source checks. Default to read-only reporting.
UI5 Version Information{{#if version}} for {{version}}{{/if}}
{{#if version}} Fetching information for UI5 version **{{version}}**... {{else}} Detecting project UI5 version and fetching information... {{/if}}
Version Detection
First, let me determine which UI5 version to query:
# Check project manifest.json
if [ -f "webapp/manifest.json" ]; then
VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("webapp/manifest.json", "utf8"); const m = t.match(/"minUI5Version"\s*:\s*"([^"]+)"/); console.log(m ? m[1] : "Not found");')
echo "Project UI5 Version (manifest.json): $VERSION"
fi
# Check ui5.yaml
if [ -f "ui5.yaml" ]; then
YAML_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("ui5.yaml", "utf8"); const m = t.match(/^\s*version:\s*"([^"]+)"/m); console.log(m ? m[1] : "Not found");')
echo "UI5 Tooling Version (ui5.yaml): $YAML_VERSION"
fi
# Check package.json
if [ -f "package.json" ]; then
PKG_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("package.json", "utf8"); const m = t.match(/"@ui5\/cli"\s*:\s*"\^?([^"]+)"/); console.log(m ? m[1] : "Not found");')
echo "UI5 CLI Version (package.json): $PKG_VERSION"
fi{{#if version}} Using specified version: **{{version}}** {{else}} Using detected project version (or latest if no project found) {{/if}}
---
Fetching Version Information
Use the **ui5-migration-specialist agent** or MCP tools to fetch:
1. **Version Details**:
- Release date
- Support status (active, maintenance, end-of-life)
- Latest patch version
2. **Release Notes**:
- New features
- Breaking changes
- Deprecations
- Bug fixes
3. **Upgrade Path**:
- Recommended upgrade route
- Migration complexity
- Required changes
4. **Compatibility**:
- Browser support
- Framework compatibility
- TypeScript support
---
**Querying version information...**
Expected output: comprehensive version details from the agent or MCP tool.
---
Manual Version Lookup (If Tools Unavailable)
If automated tools are unavailable, here's manual lookup information:
Project Version Detection
# Detect from manifest.json
MANIFEST_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("webapp/manifest.json", "utf8"); const m = t.match(/"minUI5Version"\s*:\s*"([^"]+)"/); console.log(m ? m[1] : "Not found");' 2>/dev/null || echo "Not found")
# Detect from ui5.yaml
YAML_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("ui5.yaml", "utf8"); const m = t.match(/^\s*version:\s*"([^"]+)"/m); console.log(m ? m[1] : "Not found");' 2>/dev/null || echo "Not found")
# Detect from index.html (bootstrap script)
HTML_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("webapp/index.html", "utf8"); const m = t.match(/ui5\.sap\.com\/([0-9.]+)/); console.log(m ? m[1] : "Not found");' 2>/dev/null || echo "Not found")
echo "Detected Versions:"
echo " manifest.json: $MANIFEST_VERSION"
echo " ui5.yaml: $YAML_VERSION"
echo " index.html: $HTML_VERSION"UI5 Version Resources
**Official Version Overview**:
https://ui5.sap.com/versionoverview.html
**Release Notes**:
https://ui5.sap.com/#/releasenotes
**Version-Specific Documentation**:
https://ui5.sap.com/{{version}}/UI5 Version Timeline
**Latest Versions** (as of 2025):
- **1.120.x** (Latest Stable) - Released 2024 Q4
- Status: Active development
- Support: Full support
- TypeScript: Full support with @types/openui5
- Recommended for new projects
- **1.108.x** (LTS - Long-Term Maintenance)
- Status: Maintenance mode
- Support: Extended until 2026
- Recommended for enterprise projects
- Stable, well-tested
- **1.84.x** (Older LTS)
- Status: Limited support
- Support: Ending soon
- Upgrade recommended
- **1.71.x and earlier**
- Status: End of life
- Support: None
- Upgrade required
Support Status Explained
**Active Development**:
- New features added
- Regular updates
- Full support
- Recommended for new projects
**Maintenance**:
- Critical bug fixes only
- Security patches
- No new features
- Stable for production
**End of Life (EOL)**:
- No updates
- No support
- Security risks
- Upgrade immediately
Breaking Changes by Version
**1.120.x** (from 1.108):
- Removed deprecated sap.ui.commons controls
- Changed default theme to Horizon
- Updated TypeScript definitions
- Modified OData batch handling
**1.108.x** (from 1.84):
- Removed jQuery.sap.* APIs
- Changed async loading requirements
- Updated Fiori Elements templates
- Modified manifest.json schema
**1.84.x** (from 1.71):
- Removed legacy controls
- Changed routing patterns
- Updated data binding syntax
Upgrade Recommendations
**From 1.84 → 1.120** (Recommended):
# Estimated effort: 2-4 hours
# Complexity: Medium
# Breaking changes: ~7 API changes
# Use migration specialist for guided upgrade
**From 1.108 → 1.120** (Easy):
# Estimated effort: 1-2 hours
# Complexity: Low
# Breaking changes: ~2 API changes
# Mostly theme and minor API updates
**From 1.71 → 1.120** (Complex):
# Estimated
Read more
name: ui5-version
description: Display UI5 version information, support status, release notes, and upgrade paths
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "[version]"
arguments:
- name: version
description: Optional UI5 version to query (e.g., 1.120.0, 1.108, latest). Defaults to project version.
required: falseShell Snippet Notes
- Shell snippets assume Bash on Linux/macOS, WSL2, or Git Bash.
- Install the command-specific tooling shown near each snippet before running it.
- Confirm before running commands that delete files, change ownership, deploy, or modify remote systems.
Output Contract
Return detected or requested UI5 version details, support status, upgrade notes, local evidence, and unresolved package/source checks. Default to read-only reporting.
UI5 Version Information{{#if version}} for {{version}}{{/if}}
{{#if version}} Fetching information for UI5 version **{{version}}**... {{else}} Detecting project UI5 version and fetching information... {{/if}}
Version Detection
First, let me determine which UI5 version to query:
# Check project manifest.json
if [ -f "webapp/manifest.json" ]; then
VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("webapp/manifest.json", "utf8"); const m = t.match(/"minUI5Version"\s*:\s*"([^"]+)"/); console.log(m ? m[1] : "Not found");')
echo "Project UI5 Version (manifest.json): $VERSION"
fi
# Check ui5.yaml
if [ -f "ui5.yaml" ]; then
YAML_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("ui5.yaml", "utf8"); const m = t.match(/^\s*version:\s*"([^"]+)"/m); console.log(m ? m[1] : "Not found");')
echo "UI5 Tooling Version (ui5.yaml): $YAML_VERSION"
fi
# Check package.json
if [ -f "package.json" ]; then
PKG_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("package.json", "utf8"); const m = t.match(/"@ui5\/cli"\s*:\s*"\^?([^"]+)"/); console.log(m ? m[1] : "Not found");')
echo "UI5 CLI Version (package.json): $PKG_VERSION"
fi{{#if version}} Using specified version: **{{version}}** {{else}} Using detected project version (or latest if no project found) {{/if}}
---
Fetching Version Information
Use the **ui5-migration-specialist agent** or MCP tools to fetch:
1. **Version Details**:
- Release date
- Support status (active, maintenance, end-of-life)
- Latest patch version
2. **Release Notes**:
- New features
- Breaking changes
- Deprecations
- Bug fixes
3. **Upgrade Path**:
- Recommended upgrade route
- Migration complexity
- Required changes
4. **Compatibility**:
- Browser support
- Framework compatibility
- TypeScript support
---
**Querying version information...**
Expected output: comprehensive version details from the agent or MCP tool.
---
Manual Version Lookup (If Tools Unavailable)
If automated tools are unavailable, here's manual lookup information:
Project Version Detection
# Detect from manifest.json
MANIFEST_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("webapp/manifest.json", "utf8"); const m = t.match(/"minUI5Version"\s*:\s*"([^"]+)"/); console.log(m ? m[1] : "Not found");' 2>/dev/null || echo "Not found")
# Detect from ui5.yaml
YAML_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("ui5.yaml", "utf8"); const m = t.match(/^\s*version:\s*"([^"]+)"/m); console.log(m ? m[1] : "Not found");' 2>/dev/null || echo "Not found")
# Detect from index.html (bootstrap script)
HTML_VERSION=$(node -e 'const fs = require("fs"); const t = fs.readFileSync("webapp/index.html", "utf8"); const m = t.match(/ui5\.sap\.com\/([0-9.]+)/); console.log(m ? m[1] : "Not found");' 2>/dev/null || echo "Not found")
echo "Detected Versions:"
echo " manifest.json: $MANIFEST_VERSION"
echo " ui5.yaml: $YAML_VERSION"
echo " index.html: $HTML_VERSION"UI5 Version Resources
**Official Version Overview**:
https://ui5.sap.com/versionoverview.html
**Release Notes**:
https://ui5.sap.com/#/releasenotes
**Version-Specific Documentation**:
https://ui5.sap.com/{{version}}/UI5 Version Timeline
**Latest Versions** (as of 2025):
- **1.120.x** (Latest Stable) - Released 2024 Q4
- Status: Active development
- Support: Full support
- TypeScript: Full support with @types/openui5
- Recommended for new projects
- **1.108.x** (LTS - Long-Term Maintenance)
- Status: Maintenance mode
- Support: Extended until 2026
- Recommended for enterprise projects
- Stable, well-tested
- **1.84.x** (Older LTS)
- Status: Limited support
- Support: Ending soon
- Upgrade recommended
- **1.71.x and earlier**
- Status: End of life
- Support: None
- Upgrade required
Support Status Explained
**Active Development**:
- New features added
- Regular updates
- Full support
- Recommended for new projects
**Maintenance**:
- Critical bug fixes only
- Security patches
- No new features
- Stable for production
**End of Life (EOL)**:
- No updates
- No support
- Security risks
- Upgrade immediately
Breaking Changes by Version
**1.120.x** (from 1.108):
- Removed deprecated sap.ui.commons controls
- Changed default theme to Horizon
- Updated TypeScript definitions
- Modified OData batch handling
**1.108.x** (from 1.84):
- Removed jQuery.sap.* APIs
- Changed async loading requirements
- Updated Fiori Elements templates
- Modified manifest.json schema
**1.84.x** (from 1.71):
- Removed legacy controls
- Changed routing patterns
- Updated data binding syntax
Upgrade Recommendations
**From 1.84 → 1.120** (Recommended):
# Estimated effort: 2-4 hours # Complexity: Medium # Breaking changes: ~7 API changes # Use migration specialist for guided upgrade
**From 1.108 → 1.120** (Easy):
# Estimated effort: 1-2 hours # Complexity: Low # Breaking changes: ~2 API changes # Mostly theme and minor API updates
**From 1.71 → 1.120** (Complex):
# Estimated
40 SAP development plugins with evidence-tracked verification SAP development plugins for AI coding assistants, with public-source or package-registry verification tracked where available.
Repo: secondsky/sap-skills
Other commands on sap-skills.
- /abap-cds-model-check
Optional intended usage such as analytical, transactional, reuse, value-help, or extraction
Open command - /abap-cloud-review
Optional target ABAP platform or SAP BTP ABAP Environment release
Open command - /ai-core-deployment-check
Optional runtime or scenario name, such as orchestration, serving, training, or batch
Open command - /api-style-review
Optional API style lens such as REST, OData, OpenAPI, or SDK
Open command - /btp-architecture-review
Optional scenario lens such as extension, integration, analytics, or AI
Open command - /work-zone-content-check
Optional Work Zone edition or content type
Open command

