You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to keep track of what version of modulesync was used on a given module, we should use a key/value pair somewhere in the repo's root that we can query. When paired with a version-bump script that keeps the msync version file in line with the tag/release version, this would be a more reliable method than depending on commit messages.
The text was updated successfully, but these errors were encountered:
In order to keep track of what version of modulesync was used on a given module, we should use a key/value pair somewhere in the repo's root that we can query. When paired with a version-bump script that keeps the msync version file in line with the tag/release version, this would be a more reliable method than depending on commit messages.
The text was updated successfully, but these errors were encountered: