Release ClickStack Helm Charts - #277
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
9 times, most recently
from
September 18, 2026 02:08
5777bc9 to
48e2b0e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 19, 2026 02:09
48e2b0e to
fccc476
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 20, 2026 02:09
fccc476 to
2390bca
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
helm-charts@3.4.0
Minor Changes
hyperdx.io/dashboard: "true". Discovery is scoped to the release namespace by default (a namespaced Role, no cluster-wide access); sethyperdx.dashboards.namespacesto also watch specific namespaces, orhyperdx.dashboards.namespaces: [ALL]for cluster-wide discovery. Requires feat: Add file-based dashboard provisioner hyperdxio/hyperdx#1962 (file-based dashboard provisioner).Patch Changes
8899b96: Bump
js-yamlfrom ^4.2.0 to ^5.4.1 for the release tooling (update-chart-versions.js,extract-release-notes.js). No chart changes. Both scripts continue to work via the v5 CJS build; a newversion-script-smokeCI job now exercises them at PR time so future dependency bumps cannot break releases silently. Also restores consistency betweenpackage.jsonandyarn.lock, which had drifted on main.f84b6bd: Clear all 7 dependency advisories in the release tooling. No chart changes.
js-yaml3.14.1 → 3.15.2: a second copy pulled in transitively via@changesets/cli→read→parse, carrying 3 highs and 2 moderates(quadratic CPU in merge-key/
!!omaphandling, prototype pollution in<<).The direct
js-yaml@^5.4.1dependency was already fine; this is the older copythe range already allowed to move.
tmp0.0.33 → 0.2.7 via aresolutionsoverride, clearing a high pathtraversal (
<0.2.6) and a low symlink issue.external-editordeclarestmp@^0.0.33, and a caret on a0.0.xversion is semver-equivalent to=0.0.33, so this cannot be re-resolved without the override. It calls onlytmp.tmpNameSync(), which 0.2.x still exports.Both are reachable only through the release/changeset tooling, never at chart
render time.
573b600: chore: update appVersion to 2.38.0