メニュー
A new Oracle Database version is released. It should work with the existing datafiles without requiring a dump/restore, verify and then prepare the migration guide for users.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | db-upgrade |
| description | A new Oracle Database version is released. It should work with the existing datafiles without requiring a dump/restore, verify and then prepare the migration guide for users. |
Use gh run list --workflow=test-db-upgrade.yml to check if a recent successful run of the test-db-upgrade.yml workflow exists. If not, ask the user if they want to trigger a new run with the new database version. First verify that such a version exists on the repo.
Follow the actual migration guides of similar upgrades (e.g. 26-2) to upgrade the database locally. This will involve:
Do it in a safe way and confirm that everything is working correctly before proceeding to the next step.
After a successful upgrade, create a new migration guide in docs/src/content/docs/migrations/. Use the existing guides (e.g. 25-3.md) as a template. The guide should include:
title, description, sidebar.order (increment from the previous guide)git log --oneline <last-tag>..HEAD --no-merges and git show <hash> --stat to gather the full list of commits and changed files since the last release tag (even though they where committed on the old tags branches, they are still relevant for the new version if they were committed after the last release)