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: README.md
+2-37Lines changed: 2 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,9 +79,9 @@ try {
79
79
Run `./mvnw release:prepare -DreleaseVersion=` with the version you want to create.
80
80
Push the changes including the tag.
81
81
82
-
## Publishing to Maven Central and GitHub Packages
82
+
## Publishing to Maven Central
83
83
84
-
This project is configured to publish to both Maven Central and GitHub Packages. The GitHub Actions workflow will automatically publish to both repositories when a new tag is pushed.
84
+
This project is configured to publish to both Maven Central.
85
85
86
86
### Required Secrets
87
87
@@ -92,41 +92,6 @@ To publish to Maven Central, you need to configure the following secrets in your
92
92
-`GPG_PRIVATE_KEY`: Your GPG private key for signing artifacts
93
93
-`GPG_PASSPHRASE`: The passphrase for your GPG private key
94
94
95
-
### Setting up GPG for Signing
96
-
97
-
1. Install GPG if you don't have it already:
98
-
```bash
99
-
# macOS
100
-
brew install gnupg
101
-
102
-
# Ubuntu
103
-
sudo apt-get install gnupg
104
-
```
105
-
106
-
2. Generate a GPG key pair:
107
-
```bash
108
-
gpg --full-generate-key
109
-
```
110
-
111
-
3. List your keys:
112
-
```bash
113
-
gpg --list-secret-keys --keyid-format LONG
114
-
```
115
-
116
-
4. Export your private key (replace `KEY_ID` with your key ID):
117
-
```bash
118
-
gpg --export-secret-keys --armor KEY_ID
119
-
```
120
-
121
-
5. Add the exported key to your GitHub repository secrets as `GPG_PRIVATE_KEY`
122
-
6. Add your GPG passphrase to your GitHub repository secrets as `GPG_PASSPHRASE`
123
-
124
-
### Setting up Sonatype OSSRH
125
-
126
-
1. Create an account on [Sonatype OSSRH](https://s01.oss.sonatype.org/)
127
-
2. Create a new project ticket in the [Sonatype JIRA](https://issues.sonatype.org/)
128
-
3. Add your Sonatype username and password to your GitHub repository secrets as `OSSRH_USERNAME` and `OSSRH_PASSWORD`
129
-
130
95
## Updating
131
96
132
97
1. Ensure that langfuse-java is placed in the same directory as the main [langfuse](https://github.com/langfuse/langfuse) repository.
0 commit comments