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
Copy file name to clipboardExpand all lines: doc/maintainers-guide.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,8 +49,7 @@
49
49
## Release
50
50
51
51
- The library artifacts are published to Clojars (http://clojars.org) under the `dev.data-star.clojure` namespace.
52
-
- The Clojars account is managed by Ben Croker, the DNS verification is managed by Delaney.
53
-
- The Clojars deploy token is also managed by Ben and added to this repo as a GH Actions Secret
52
+
- The Clojars account and deploy token are managed by Ben Croker, and added to this repo as GitHub action secrets:
54
53
- Secret name: `CLOJARS_USERNAME`
55
54
Value: _the clojars account username_
56
55
- Secret name: `CLOJARS_PASSWORD`
@@ -59,7 +58,7 @@
59
58
60
59
The Github Actions [CI workflow for clojure](../.github/workflows/release-sdk.yml) will always run the tests and produce jar artifacts.
61
60
62
-
Triggering a deployment to clojars is a manual process. A Datastar core contributor must trigger the Clojure SDK workflow with the `publish` input boolean set to `true.
61
+
Triggering a deployment to clojars is a manual process. A Datastar core contributor must trigger the `Release Clojure SDK` workflow with the `publish` input boolean set to `true`.
0 commit comments