-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]Unknown manifest field "upgrade_policy" #13182
Labels
bug
Something isn't working
Comments
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? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃悰 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:
The text was updated successfully, but these errors were encountered: