New releases of Iron Vault may change how it represents different information present in your vault. The two main reasons for this are:
Whenever you open a vault with Iron Vault installed, Iron Vault will check your vault to determine if any migrations are needed. You can also trigger this check by running the "Check if vault data migration is needed" command.
Iron Vault is only designed to work with vaults compatible with the current release. Using Iron Vault commands on an unmigrated vault may have unpredictable results.
When Iron Vault detects that your vault needs a migration, you will be prompted to generate a migration report:
If you choose yes, the plugin will generate a preview Migration report which you can use to understand the changes it will make in your vault. If you are satisfied with the report, run the "Check if vault data migration is needed" command again and this time choose "no" for the report.
If you choose no, you will then see a new prompt, asking you if you wish to allow the migration:
You should make a back up of your vault before running a migration. We design the migrations carefully and test them before release, but, because they can rewrite all files in your vault, you should keep a backup to guard against a migration causing data loss.
If you choose "yes", your vault will be migrated to the latest version. A Migration report will be generated so you can see what changes were actually made to your vault.
Migration reports detail the changes made (or, in the case of previews, the changes that would be made) in a migration. You can review a preview log before
In this case, a Datasworn version change has changed the IDs used by various oracles, and the ids for these oracles are being updated to match the current version.