...
Uploading a new version follows the same steps as uploading a file for the first time. Use the same file name and store it in the same location. It is recommended to add a comment to the new version in order to easily track differences at a glance.
...
Uploading a new version follows the same steps as uploading a file for the first time. Use the same file name and store it in the same location. It is recommended to add a comment to the new version in order to easily track differences at a glance. Version comments are available in Python and R clients, but not in the command line client.
...
If you are using the Synapse UI to update your files, adding or editing annotations and provenance will not update the file version. Refer to the Annotations and Queries article
Refer to /wiki/spaces/DOCS/pages/2667708522 for instructions on adding/editing annotations via the web clientSynapse UI.
If you are using programmatic clients to update your files, any change to a file will automatically update the version, including changes to annotations and provenance. In some rare cases, you may not want to create a new version when you make changes to a file. The main function for storing or updating an entity in the Python and R clients is the store function (see the Python docs or R docs for more information). This function takes an optional forceVersion parameter, whose default value is True. This means that whenever store is called to update an existing entity, the version is increased even if nothing has changed on the entity. If you specifically do not want to change the version when using the store function, include a forceVersion=False parameter.
...
Setting Provenance Without Changing Versions
Please refer to the Provenance article for Refer to /wiki/spaces/DOCS/pages/1972470373 for instructions on adding/editing provenance via the Synapse UI.
...