Treora commented on issue #92: URL: https://github.com/apache/incubator-annotator/issues/92#issuecomment-754737777
> I'd be interested in using some of these non-versioned releases. Are there any constraints around publishing a "latest" build? Would you be open to a pr that does it in GH actions? I was just looking yesterday at the status of yarn 2, to see if I could use that to directly depend on this git repository (as explained above, our monorepo/multi-package structure makes it impossible to depend on using yarn 1 or npm). I don’t know if @tilgovi has gotten further with this? In any case, even though directly depending on the git repo seems more elegant, it might take a while for us to move to yarn 2 (or not?), and it would force people to use yarn 2 until (if) monorepo dependencies are supported more widely. So to be pragmatic I think we should just auto-publish on npm indeed. I’d tag it `dev` instead of `latest`, to be clear it is not the latest release. PRs would probably be very welcome! It depends on @tilgovi who was looking into this, but I don’t think we had anything set up yet. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
