Open brmataptos opened 2 weeks ago
Because third-party needed to be agnostic until recently, this must have been kept out of it as it is aptos specific. Moving forward we replace the package system so I don't think this bug should be kept.
Are you saying that you have expect that it will be fixed, so this bug should be closed?
🐛 Bug
The field "upgrade_policy" appears in a number of Aptos Move examples and e2e-move tests, but the manifest_parser doesn't know about it. It shows up as a warning when processing the
Move.toml
file (try --nocapture when running aptos-move-examples tests). As this field is documented (see https://aptos.dev/move/book/package-upgrades/#how-it-works) it should be supported in third_party/move/tools/move-package/src/source_package/manifest_parser.rs.Here are the tests including it: