Skip to content

Commit

Permalink
release instrumentation-openai 0.4.0 (#474)
Browse files Browse the repository at this point in the history
Fix the release workflow to install deps and compile before published,
otherwise a mostly empty package is published.
  • Loading branch information
trentm authored Dec 12, 2024
1 parent 441bfd0 commit b465fc4
Show file tree
Hide file tree
Showing 4 changed files with 15 additions and 3 deletions.
6 changes: 6 additions & 0 deletions .github/workflows/release-instrumentation-openai.yml
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,12 @@ jobs:
node-version: 'v18.20.4'
registry-url: 'https://registry.npmjs.org'

- run: npm ci
working-directory: ${{ env.PKGDIR }}

- run: npm run compile
working-directory: ${{ env.PKGDIR }}

- run: npm publish
working-directory: ${{ env.PKGDIR }}
env:
Expand Down
6 changes: 6 additions & 0 deletions packages/instrumentation-openai/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,13 @@
# @elastic/opentelemetry-instrumentation-openai Changelog

## v0.4.0

- Fix the release workflow.

## v0.3.0

(Broken release. Use v0.4.0 or later.)

- Based on GenAI semantic conventions 1.29.
- Instrumentation of chat completion, including streaming and tool calls.
- Instrumentation of [embeddings creation](https://platform.openai.com/docs/api-reference/embeddings/create).
Expand Down
4 changes: 2 additions & 2 deletions packages/instrumentation-openai/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/instrumentation-openai/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@elastic/opentelemetry-instrumentation-openai",
"version": "0.3.0",
"version": "0.4.0",
"description": "OpenTelemetry instrumentation for the `openai` OpenAI client library",
"type": "commonjs",
"publishConfig": {
Expand Down

0 comments on commit b465fc4

Please sign in to comment.