Bump posthog-node from 5.28.9 to 5.28.11 - #5
Merged
NiveditJain merged 1 commit intoApr 6, 2026
Conversation
Bumps [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) from 5.28.9 to 5.28.11. - [Release notes](https://github.com/PostHog/posthog-js/releases) - [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md) - [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.28.11/packages/node) --- updated-dependencies: - dependency-name: posthog-node dependency-version: 5.28.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
failproofversionmanager Bot
pushed a commit
that referenced
this pull request
Jul 17, 2026
Upstream: Document agenteye-evaluator in README and CONTRIBUTING (#5) FailproofAI/skills@de31dec
6 tasks
SiddarthAA
added a commit
that referenced
this pull request
Aug 21, 2026
… env vars
Three pages told the reader the Cloud CLI cannot do what it does:
docs/policies/deploy.mdx "Cloud deployment endpoints are intentionally
not exposed as ordinary `fp` commands"
docs/policies/editor.mdx "The Cloud CLI does not publish policy versions"
docs/start/first-policy.mdx "does not expose root-only enforcement
deployment routes"
Each then sent the reader to the dashboard. All three are false, and were
disproved by running the commands against a live stack: `fp policies publish`
minted a version, `fp fleet deploy` moved a machine to deployment #5, and
`fp fleet show/diff/history/rollback`, `fp policies list/show/enable/disable/
delete/test/compose` and `fp guardrails summary/timeline` all work.
The `docs/reference/cloud-cli.mdx` environment table was worse, because its
failure is silent. It named AGENTEYE_DASHBOARD_URL, AGENTEYE_ORG,
AGENTEYE_CLI_TOKEN, AGENTEYE_CLI_API_KEY, AGENTEYE_CLI_JSON, AGENTEYE_INSECURE,
AGENTEYE_HOME and AGENTEYE_ANALYTICS_DISABLED. The CLI declares FP_* in
fp_cli/app.py, and an unknown environment variable is not an error, so:
AGENTEYE_DASHBOARD_URL=http://127.0.0.1:59999 fp policies list -> exit 0
FP_DASHBOARD_URL=http://127.0.0.1:59999 fp policies list -> exit 3
Both verified live. That table is where somebody points the CLI at their own
deployment, so being quietly ignored and running against the saved dashboard
instead is the worst outcome available.
Every command now shown on these pages was executed before being written down.
A callout records that AGENTEYE_HOME and AGENTEYE_ENVIRONMENT do still exist,
but belong to the collector and the telemetry SDK rather than to this CLI.
The translated copies under docs/<lang>/ still carry the old text; they are out
of scope here, as elsewhere in this release.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Bumps posthog-node from 5.28.9 to 5.28.11.
Release notes
Sourced from posthog-node's releases.
Changelog
Sourced from posthog-node's changelog.
Commits
8571c13chore: update versions and lockfile [version bump]356fb33chore: update versions and lockfile [version bump]Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)