Update skipper version, step 2/2

[RomanZavodskikh]

Merge #7648 before this one

• config: support multiple default filters flag values config: support multiple default filters flag values zalando/skipper#3084
• build(deps): bump docker/login-action from 3.1.0 to 3.2.0 build(deps): bump docker/login-action from 3.1.0 to 3.2.0 zalando/skipper#3090
• build(deps): bump github.com/redis/go-redis/v9 from 9.5.1 to 9.5.2 build(deps): bump github.com/redis/go-redis/v9 from 9.5.1 to 9.5.2 zalando/skipper#3092
• build(deps): bump github.com/open-policy-agent/opa-envoy-plugin from 0.64.1-envoy to 0.65.0-envoy build(deps): bump github.com/open-policy-agent/opa-envoy-plugin from 0.64.1-envoy to 0.65.0-envoy zalando/skipper#3093
• metrics: add start label for prometheus counters metrics: add start label for prometheus counters zalando/skipper#3089
• Reduce errors in decision logs that are operational Reduce errors in decision logs that are operational zalando/skipper#3086
• doc: review and update ingress usage docs doc: review and update ingress usage docs zalando/skipper#3094
• build: trim path build: trim path zalando/skipper#3095
• OPA: Add decision outcome to span OPA: Add decision outcome to span zalando/skipper#3096
• Set log level of PHC dropping an endpoint to debug Set log level of PHC dropping an endpoint to debug zalando/skipper#3098

FYI zalando/skipper@v0.21.101...v0.21.108

[AlexanderYastrebov]

Does it target a wrong branch?

[RomanZavodskikh]

@AlexanderYastrebov

Does it target a wrong branch?

No, it does target the right branch because:

• this particular PR is simple in every point in time (1 line removed, 1 line added)
• after merging the corresponding canary PR it is automatically redirected to be merged into dev.

If the PR is created to dev from the very beginning, the UI will show 2 lines added and 2 lines removed even after canary PR merged which could be confusing.

[RomanZavodskikh]

👍

[AlexanderYastrebov]

👍