Skip to content

feat: sync main 1.39 into v1 - #405

Merged
eli-r-ph merged 5 commits into
v1from
eli/v1-sync-main-1.39
Nov 2, 2026
Merged

eli-r-ph merged 5 commits into
v1from
eli/v1-sync-main-1.39

Conversation

@eli-r-ph

@eli-r-ph eli-r-ph commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

💡 Motivation and Context

main released 1.39.0 after the last sync (#390), so v2 would drop its new flags API (UnresolvedFlags, UnresolvedFlagReason*, FeatureFlagErrorLocalEvaluationInconclusive and the Reason fields) and break 1.39 users on upgrade.

Changes

💚 How did you test it?

📝 Checklist

  • All commits are signed (see Commit signing)
  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

If releasing new changes

  • Ran pnpm changeset to generate a changeset file

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

🤖 Generated with Claude Code

gustavohstrassburger and others added 4 commits November 1, 2026 13:22
…#396)

* feat(flags): report unresolved local flags on EvaluateFlags snapshots

Implements the "Snapshot unresolved flag reporting" and "Warning for flags local evaluation never resolves" requirements of the evaluate-flags spec (PostHog/sdk-specs#85).

- Add `FeatureFlagEvaluations.UnresolvedFlags()`, with an `UnresolvedFlagReason` for each flag and the spec's fixed precedence.
- Report `local_evaluation_inconclusive` instead of `flag_missing` when a snapshot read hits an unresolved flag.
- Do not stop a condition at the first inconclusive filter, so a filter that does not match resolves the condition locally.
- Check `Active` before experience continuity.
- Log one warning per flag that local evaluation can never resolve, repeated only when its definition changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Generated-By: PostHog Desktop
Task-Id: 39793b31-809e-4689-a5d8-b4359cbb22c1

* fix(flags): address review findings for unresolved local flags

* fix(flags): sort payload keys when fingerprinting unresolvable flags

* test(flags): cover server fallback when a flag dependency needs server data

* fix(flags): rank unresolved reasons across the whole flag on server fallback

* fix(flags): report a missing group key as missing context

(cherry picked from commit 401e68f)
v2 sends events to the capture v1 endpoint, which needs a success body
for the client to report delivery. Use the shared serveCaptureOK helper
as the other evaluation test servers do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps the github-actions group with 2 updates: [github/codeql-action/init](https://github.com/github/codeql-action) and [github/codeql-action/analyze](https://github.com/github/codeql-action).

Updates `github/codeql-action/init` from 4.39.0 to 4.39.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@6f2ac81...9b32540)

Updates `github/codeql-action/analyze` from 4.39.0 to 4.39.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@6f2ac81...9b32540)

---
updated-dependencies:
- dependency-name: github/codeql-action/init
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
(cherry picked from commit fee6566)
@eli-r-ph
eli-r-ph requested a review from a team November 1, 2026 21:40

@marandaneto marandaneto left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated advisory code review.

Comment thread featureflags.go Resolved
Comment thread posthog.go Resolved
@marandaneto
marandaneto requested a review from a team November 2, 2026 15:31

@turnipdabeets turnipdabeets left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] The two findings from the automated review are in #396's code, which is the same on main, so this sync didn't introduce them. We should fix them on main and carry the fix into v1 with the next sync.

@eli-r-ph
eli-r-ph merged commit ed7b4fa into v1 Nov 2, 2026
32 checks passed
@eli-r-ph
eli-r-ph deleted the eli/v1-sync-main-1.39 branch November 2, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants