Skip to content

Commit fe24fc6

Browse files
committed
chore: buil dupdates
1 parent 2a89561 commit fe24fc6

File tree

2 files changed

+2
-50
lines changed

2 files changed

+2
-50
lines changed

README.md

Lines changed: 2 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -79,9 +79,9 @@ try {
7979
Run `./mvnw release:prepare -DreleaseVersion=` with the version you want to create.
8080
Push the changes including the tag.
8181

82-
## Publishing to Maven Central and GitHub Packages
82+
## Publishing to Maven Central
8383

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.
8585

8686
### Required Secrets
8787

@@ -92,41 +92,6 @@ To publish to Maven Central, you need to configure the following secrets in your
9292
- `GPG_PRIVATE_KEY`: Your GPG private key for signing artifacts
9393
- `GPG_PASSPHRASE`: The passphrase for your GPG private key
9494

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-
13095
## Updating
13196

13297
1. Ensure that langfuse-java is placed in the same directory as the main [langfuse](https://github.com/langfuse/langfuse) repository.

pom.xml

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -42,19 +42,6 @@
4242
</properties>
4343

4444
<profiles>
45-
<profile>
46-
<id>github</id>
47-
<activation>
48-
<activeByDefault>true</activeByDefault>
49-
</activation>
50-
<distributionManagement>
51-
<repository>
52-
<id>github</id>
53-
<name>GitHub Packages</name>
54-
<url>https://maven.pkg.github.com/langfuse/langfuse-java</url>
55-
</repository>
56-
</distributionManagement>
57-
</profile>
5845
<profile>
5946
<id>ossrh</id>
6047
<distributionManagement>

0 commit comments

Comments
 (0)