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
As of today your last published release is 44 commits behind master.
This is somewhat annoying as none of the links provided lead to the most up to date escript.
How about setting up your CI to publish the escript when building tags?
Then you'd need to cut tags more often.
You could also do that automatically by having your CI push a tag when a new commit lands in the master branch.
The text was updated successfully, but these errors were encountered:
Current version has only one feature we merged few weeks ago but those changes had some issues (timeline tracking). Right now we have one issue with frontend caching. I'll try to focus on that in the following days and we will try to cut release.
To be honest I don't like this kind of automation because we're not adding that many features/changes to project to have to automate that.
As of today your last published release is 44 commits behind master.
This is somewhat annoying as none of the links provided lead to the most up to date escript.
How about setting up your CI to publish the escript when building tags?
Then you'd need to cut tags more often.
You could also do that automatically by having your CI push a tag when a new commit lands in the master branch.
The text was updated successfully, but these errors were encountered: