Ariel Gadbois-Roy

Enum arrays are broken in plugin-generated metadata

3

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When a model's property is an array of an enum, the...

fix(core): isArray always false for enum arrays in plugin metadata

4

## PR Checklist Please check if your PR fulfills the following requirements: - [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md - [x] Tests for the changes have been added...

Updating AWS::CloudFront::PublicKey results in BadRequest error

7

### Name of the resource AWS::CloudFront::PublicKey ### Resource Name _No response_ ### Issue Description Updating the key value of a AWS::CloudFront::PublicKey resource results in a BadRequest error instead of recreating...

🐛 Cloudflared ignores the initial version of a remote config

5

**Describe the bug** Cloudflared ignores the first version of the remote config. https://github.com/cloudflare/cloudflared/blob/master/orchestration/orchestrator.go#L43 This comment indicates that remote config versions are always superior to `0`, yet a remote configs created...

Unsecured cloudflared service tunnel secret storage on Windows

1

I really like the centralized configuration feature of Cloudflare Tunnel. The recommended way to run a tunnel as a service on Windows is to use `cloudflared service install `, where...

Cannot use $store.dispatch on a named static module

3

Hi, I need my static module to have a name in order to be able to use `getModule` on it. However, doing so prevents my legacy code from using `$store.dispatch`...

**Description** Add the missing attributes of the Project schema that are marked as "Premium" or "Ultimate" in the Gitlab docs (e.g `merge_requests_template`). https://docs.gitlab.com/ee/api/projects.html#templates-for-issues-and-merge-requests Other "Premium" attributes such as `mirror_trigger_builds` are...

Update forge-server-utils to version 9.x.x

2

Updating the `forge-server-utils` dependency to version 9.x.x would allow developers to get rid of vulnerable sub-dependencies, such as `[email protected]`. 

Empty arrays stripped from my request bodies, even when they are specified as "required" in the schema. Is this the intended behavior? https://github.com/readmeio/oas/blob/main/packages/oas-to-har/src/index.ts#L442 https://github.com/readmeio/remove-undefined-objects/blob/5.0.0/src/index.ts#L27 My current workaround is the following...