nocobase-app-upgrade SKILL.md skillA
nocobase-app-upgrade from nocobase/nocobase is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nocobase/nocobase/nocobase-app-upgrade@git:20261028.d3f0c92Pins git:20261028.d3f0c92 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nocobase/nocobase
- Path
packages/app/app-skills/skills/nocobase-app-upgrade/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.d3f0c92, committed Oct 28, 2026
- First version recorded
- Oct 26, 2026
- Size
- 23,027 bytes
- Repository stars
- 24,822
- License
- none declared
Upgrade this application to a newer release of the template it was generated from, which is how this application moves to a newer NocoBase version. Users rarely think in terms of templates, so use it whenever the user asks to upgrade or update NocoBase, the NocoBase core, kernel or framework version, or the @nocobase packages as a whole — for example "upgrade NocoBase", "update the NocoBase core version", "move to the latest NocoBase release", "升级 NocoBase", "升级 NocoBase 内核版本…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Upgrading the application template `pnpm create @nocobase/app` copied a template into the user's hands and left no link back to it, so a newer template release arrives only by someone merging it in. The difficulty is telling the template's changes from the user's. Comparing the application against the latest template cannot: a file that differs may have been changed by either side, or both. So compare the two template _releases_ instead — the baseline already merged and the target — and decide file by file how each of their differences lands here. ```text BASE nocobase.defaultTemplateVersion — the release already merged in TARGET the release being moved to PROJECT the application as the user has it now BASE → TARGET what the template changed — the work to bring in BASE → PROJECT what the user changed — the work that must survive ``` `defaultTemplateVersion` is not the application's `version`. It records how far template source has been merged, and moves only after a merge actually happens. …
Read the whole file at its exact version.
How to install
mdr add nocobase/nocobase/nocobase-app-upgrade@sha256:c0d3e5f4864af1c1The line at the top of this page pins the label git:20261028.d3f0c92, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wk2ht42d5hte6dml)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 26, 2026 and Oct 28, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.d3f0c92 latest | 2026-10-28 | d3f0c92 | 23,027 B | A | view · diff |
| git:20261028.e3d9a52 | 2026-10-28 | e3d9a52 | 22,362 B | A | view · diff |
| git:20261027.451bf75 | 2026-10-27 | 451bf75 | 18,298 B | A | view · diff |
| git:20261027.df09e63 | 2026-10-27 | df09e63 | 18,019 B | A | view · diff |
| git:20261026.54af55a | 2026-10-26 | 54af55a | 17,255 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23027 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nocobase/nocobase · 24,822 stars · license none declared · pushed 2026-11-03 · branch v3-develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_wk2ht42d5hte6dml GET https://markdownregistry.com/api/v1/resolve?ref=nocobase/nocobase/nocobase-app-upgrade GET https://markdownregistry.com/api/v1/blob/c0d3e5f4864af1c1640906572aa19b815dcd3e13ca0de3eda5845ee38c6e8d2a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.