[NA] [HELM] [SDK] Update versions to 2.2.33 and bump base version to 2.2.34 - #7933
Merged
Conversation
JetoPistola
marked this pull request as ready for review
August 20, 2026 11:49
Contributor
⏱️ pre-commit per-hook timing
⏭️ 42 skipped (no matching files changed)
|
Collaborator
|
No test needed here. Version-only bump: Chart.yaml version/appVersion 2.2.32 -> 2.2.33, the six TypeScript SDK package.json versions to match, and version.txt to 2.2.34. The seven package-lock.json diffs are just each package's own Advisory, from the QA test radar. Nothing here blocks this PR, and anything it proposes is a draft for review. |
thiagohora
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Details
Manual replacement for the version bump that the
Releaseworkflow normally commits itself — same repair as #7905, one release later. The2.2.33tag was created on 2026-08-20 (commit e50e4a5) by run 32351462704, but that run failed on the npm publish jobs, socommit-all-version-changeswas skipped andmainnever recorded 2.2.33 as shipped.This commit is a byte-for-byte reproduction of what that job would have produced — the same 15 files, same tools, same commit message:
sdks/typescript+ the five TS integrations (opik-openai,opik-gemini,opik-langchain,opik-vercel,opik-otel) →2.2.33, vianpm version --no-git-tag-versiondeployment/helm_chart/opik/Chart.yamlversion+appVersion→2.2.33deployment/helm_chart/opik/README.mdbadges regenerated with helm-docs1.14.2(the version pinned in.pre-commit-config.yaml), so theupdate_helm_readme.yamlgate stays green for the next chart PRversion.txt→2.2.34, the next version a release run will cut fromset-versionNothing is published or deployed here. Note that unlike #7905,
mainwas not left internally inconsistent — the previous bump (b957a9a) landed cleanly, so this PR advances a consistent2.2.32state to2.2.33rather than repairing a split one.Why not simply replay the release
A re-run with
reuse_existing_tag: truewould get pastcreate-git-tag, but most of 2.2.33 is already published and the re-publish is not uniformly idempotent:latestlateststill2.2.32Replaying would re-attempt the PyPI upload for a version that already exists (PyPI refuses re-uploads) and needlessly re-push the chart and rebuild images. This PR closes the last row only; the npm packages and the GitHub release are tracked as follow-ups below.
Known follow-ups (not in this PR)
opikand all five integrations are still at2.2.32on the registry. Needs a targeted publish once the OIDC/publish fixes ([DND-1565] ci: grant id-token to the release wrapper so npm OIDC works #7932, merged; [DND-1562] ci: harden the TypeScript publish composite action against template injection #7918) are in place.2.2.31or2.2.33, and a stray untagged draft (untagged-1c65a48b93f3) from 2026-08-19. Both gaps line up with the failed runs and want a retroactive cleanup.Change checklist
Issues
[NA].AI-WATERMARK
AI-WATERMARK: yes
commit-all-version-changessteps from.github/workflows/release.yamlverbatim (npm version, sed on Chart.yaml, pinned helm-docs, the +1 patch rule), plus this PR description. No hand-written source changes.Testing
No application code changed — only version strings. Verification performed:
commit-all-version-changesruns —npm version 2.2.33 --no-git-tag-version(Node 20, matching the job'ssetup-node), the twosedsubstitutions onChart.yaml,jnorwood/helm-docs:v1.14.2via Docker for the chart README, and the job's+1patch script forversion.txt(2.2.33 → 2.2.34). Files staged with the job's exactgit addset and committed with its exact message template.git diff --numstathere is identical, file for file, to the last automated bump commit b957a9a ("Update versions to 2.2.32 and bump base version to 2.2.33") —Chart.yaml2/2, chartREADME.md1/1 (badge line only), sixpackage.json1/1, sixpackage-lock.json2/2 (root +packages[""]),version.txt1/1."version": "2.2.32"→2.2.33inpackage.json, 6× the nestedpackages[""]copy in the lockfiles, the twoChart.yamlkeys, the README badge line, andversion.txt. No dependency churn in the lockfiles.⚓ helm-docspre-commit hook passed on the commit, confirming the regenerated chart README matchesChart.yaml.opik==2.2.33present,latest), npm (opikand all five integrations top out at2.2.32), the published helm index (2.2.33present), and the GitHub releases API (no2.2.33).Generate helm docsjob to confirm the regenerated chart README is up to date.Documentation
None required — no user-facing or documented behaviour changes. The only doc touched is the generated chart README badge line.