Skip to content

fix: omitempty targeting field in Flag structure - #247

Merged
beeme1mr merged 1 commit into
open-feature:mainfrom
skyerus:issue-246_targeting-omitempty
Jan 5, 2023
Merged

beeme1mr merged 1 commit into
open-feature:mainfrom
skyerus:issue-246_targeting-omitempty

Conversation

@skyerus

@skyerus skyerus commented Jan 5, 2023

Copy link
Copy Markdown
Contributor

This PR

Added omitempty to the json tags of the targeting field in the Flag structure.

Related Issues

Fixes #246

Notes

Follow-up Tasks

How to test

Signed-off-by: Skye Gill <gill.skye95@gmail.com>
@beeme1mr
beeme1mr self-requested a review January 5, 2023 17:04
@beeme1mr
beeme1mr merged commit 3f406b5 into open-feature:main Jan 5, 2023
beeme1mr pushed a commit that referenced this pull request Jan 6, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.3.0](v0.2.7...v0.3.0)
(2023-01-06)


### ⚠ BREAKING CHANGES

* consolidated configuration change events into one event
([#241](#241))

### Features

* consolidated configuration change events into one event
([#241](#241))
([f9684b8](f9684b8))
* support yaml evaluator
([#206](#206))
([2dbace5](2dbace5))


### Bug Fixes

* changed eventing configuration mutex to rwmutex and added missing lock
([#220](#220))
([5bbef9e](5bbef9e))
* omitempty targeting field in Flag structure
([#247](#247))
([3f406b5](3f406b5))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
raphael-wigoutschnigg-dt pushed a commit to open-feature-forking/flagd that referenced this pull request Mar 11, 2025
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
toddbaert added a commit that referenced this pull request Jul 20, 2026
## Summary

Resolves all cleanly patchable open Dependabot security alerts (28 of
33). The remaining 5 have no available patched version for their legacy
import path — see below.

## Dependabot Alerts Resolved

| Alert | Package | Severity | Fix |
|-------|---------|----------|-----|
| #260 | `github.com/sigstore/sigstore-go` | **medium** | Bumped to
v1.2.2 in `test/integration` |
| #247-#259 (13 alerts) | `golang.org/x/crypto` |
**critical/high/medium** | Already resolved on `main` (v0.52.0+);
carried through the rebase |
| #207 | `js-yaml` | **medium** | Bumped to `^4.2.0` in `playground-app`
|
| #206, #202, #201 | `golang.org/x/net` | **medium** | Bumped to
v0.55.0/v0.56.0 across `flagd`, `core`, `flagd-proxy`,
`test/integration`, and related test modules |
| #200, #199 | `vite` | **medium/high** | Bumped to `^6.4.3` in
`playground-app` |
| #197 | `@babel/core` | **low** | Forced `>=7.29.6` via npm override in
`playground-app` |
| #189, #192-#196 | `github.com/containerd/containerd/v2` |
**high/medium** | Bumped to v2.2.5 in `test/integration` (kept on
`testcontainers-go` v0.41.0 — see note below) |
| #190 | `js-cookie` | **high** | Forced `>=3.0.7` via npm override in
`playground-app` |

**Note on containerd fix:** an earlier revision of this branch bumped
`testcontainers-go` to v0.43.0 to reach patched `containerd/v2`, but
that also changed `DockerContainer.MappedPort`'s signature in a way
that's incompatible with `go-sdk-contrib/tests/flagd/v2@v2.0.2` (pinned;
no newer version exists) — breaking `go vet`/`go test` compilation in
`test/integration` (not caught by `go build` alone, since it doesn't
compile `_test.go` files). Reverted `testcontainers-go` to v0.41.0
(API-compatible) while keeping `containerd/containerd/v2` pinned at
v2.2.5 via an explicit `go.mod` require — standard Go MVS, no `replace`
directive needed.

## Unresolvable Alerts

**`github.com/docker/docker`** (#151, #152, #184, #185, #186) in
`test/integration`: pinned at `v28.5.2+incompatible`. No version ≥ that
(including the advisory's referenced `v29.3.1` for #152) exists under
the legacy `github.com/docker/docker` import path in the Go module proxy
— moby now ships new majors under `github.com/moby/moby/v2`. Transitive
dependency of testcontainers/buildx/compose; unresolvable until those
upstreams migrate.

| Alert | Package | Severity | Reason |
|-------|---------|----------|--------|
| #186 | `github.com/docker/docker` | **high** | No patched version in
Go module proxy |
| #185 | `github.com/docker/docker` | **medium** | No patched version in
Go module proxy |
| #184 | `github.com/docker/docker` | **high** | No patched version in
Go module proxy |
| #152 | `github.com/docker/docker` | **high** | Advisory's patched
version (29.3.1) not published for this import path |
| #151 | `github.com/docker/docker` | **medium** | No patched version in
Go module proxy |

## Other changes

- Added `ReadTimeout` to the flagd-proxy metrics server's `http.Server`
(`flagd-proxy/pkg/service/server.go`) per CodeRabbit review feedback,
hardening the plain HTTP/h2c port against slow-client resource
exhaustion.

## Verification

- `make test`, `make build`, and `go vet` pass across all Go modules
(`core`, `flagd`, `flagd-proxy`, `flagd-proxy/tests/loadtest`,
`test/zero-downtime-flagd-proxy`).
- `test/integration`: `go build ./...`, `go vet ./...`, and `go test`
(compile-only; actual container run needs a Docker daemon) all pass.
- `playground-app`: `npm run build` succeeds; `npm install
--package-lock-only --dry-run` reports up to date.

---------

Signed-off-by: Jonathan Norris <jonathan.norris@dynatrace.com>
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Co-authored-by: Todd Baert <todd.baert@dynatrace.com>
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.

[BUG] Marshalling eval.Flags struct to JSON triggers "invalid JSON file" error

3 participants