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
I noticed a new version was released on TestFlight but no new commits were added to reflect the changes made.
Can we please see the changeset when changes are released by committing to this repo?
Ideally, TestFlight versions can be created in CI, as a GitHub action and the application can be aware of the git commit hash (as proposed in #565) and represent this information in non-production releases for easier debugging.
The text was updated successfully, but these errors were encountered:
It looks like another build (168) was released and no confirmation of what changed in the GitHub repository. Can we please look into this @creepymonster ?
I noticed a new version was released on TestFlight but no new commits were added to reflect the changes made.
Can we please see the changeset when changes are released by committing to this repo?
Ideally, TestFlight versions can be created in CI, as a GitHub action and the application can be aware of the git commit hash (as proposed in #565) and represent this information in non-production releases for easier debugging.
The text was updated successfully, but these errors were encountered: