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
The only way I could figure out of using matrix was to just copy the sources onto the classpath in my own project.
There's a way to setup github actions (or other code building services that are free to use for open source libraries) so that when a git tag is added to indicate a "release", that artifacts can be built and published on clojars/npm etc so that the library can be used just by adding a dependency to your project.clj/deps.edn.
Would you be interested in having a scheme like this? (I'm happy to implement). That way, whenever you're happy the code looks in good enough shape for a release, as an admin, you can then cut releases just by filling out the form here https://github.com/kennytilton/matrix/releases/new. I'm most interested in getting releases for the clj version at the moment but I don't think it would be a problem to build artifacts for all platforms and publish them to their respective package repos.
The text was updated successfully, but these errors were encountered:
The only way I could figure out of using matrix was to just copy the sources onto the classpath in my own project.
There's a way to setup github actions (or other code building services that are free to use for open source libraries) so that when a git tag is added to indicate a "release", that artifacts can be built and published on clojars/npm etc so that the library can be used just by adding a dependency to your project.clj/deps.edn.
Would you be interested in having a scheme like this? (I'm happy to implement). That way, whenever you're happy the code looks in good enough shape for a release, as an admin, you can then cut releases just by filling out the form here https://github.com/kennytilton/matrix/releases/new. I'm most interested in getting releases for the clj version at the moment but I don't think it would be a problem to build artifacts for all platforms and publish them to their respective package repos.
The text was updated successfully, but these errors were encountered: