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
having automatic tagging and deployment of new builds seems trickier and more fraught with peril, so i think we'd still be manually releasing new builds, and wouldn't necessarily have a clear indication of when to do so, since there's no easy way to see what dependencies changed, afaict. but it still seems useful, and potentially not a huge effort, to see when the build would break.
The text was updated successfully, but these errors were encountered:
off-hand, the two types of update i can think of are:
./gradlew wrapper --gradle-version=latest --distribution-type=bin
and check in the artifacts from that, per instructions added in README: corrections and clarifications of build instructions, formatting touchups #71.build.gradle
. or maybe just a fresh build using the constraints/pinnings in that file?i think either would use the same hook as e.g. the poetry updates in was-pywb, see https://github.com/sul-dlss/was-pywb/blob/main/.autoupdate/preupdate
having automatic tagging and deployment of new builds seems trickier and more fraught with peril, so i think we'd still be manually releasing new builds, and wouldn't necessarily have a clear indication of when to do so, since there's no easy way to see what dependencies changed, afaict. but it still seems useful, and potentially not a huge effort, to see when the build would break.
The text was updated successfully, but these errors were encountered: