Add release notes to `publish`
Julian
It would be great if there was an option for
publish
that allowed adding release notes, something like:expo publish ... -m "Bug fixes & performance improvements"
Then this could be referenced in the app to let the user why an update was needed, or what new functionality is available.
It could be as simple as a string, or as complicated as an arbitrary object, which would allow fancy things like update types (new feature vs bug fix), title, message, and possibly more.
Another way to handle this is allowing a "What's New" object in app.json.
Now that I write this, I realize I can probably just have a json file with updates in it, but I'll post this anyway in case other people have the same idea.
D
David Biller
you can update app.json. Sure. Use the extra field:
"extra": {
"versionName": "082",
"nodes": "something"
}
Mohammad H
Sounds like that could be done fairly easily in the app site rather than implementing in expo; specially your later idea. One idea: 1) in a directory say 'release_notes', you write notes for each version like 1.1.0 (filename). In the runtime, you can read the version from package.json or app.json and based on the version you read from the corresponding file and show it to users. Using this mechanism you can have a whole change logs in the app too. I think, if you use package.json, you can also show that dialog after OTA too. But you can't update in app.json until rebuilding and republishing.
D
David Biller
Mohammad H: update the app.json works... only the SDK is not possible
Mohammad H
David Biller: Sorry, not sure I fully understood. Are you saying update in app.json reflects in OTA update?
D
David Biller
Mohammad H: Yes. if you change the extra field, it is possible to get the new data OTA
Mohammad H
David Biller: Ah I see. Great to know. So I guess then this can be done by updating package.json or app.json.