Problem

The documentation states that gitlab.secure has a default value of false:

gitlab.secure: Flag to disable server certificate verification (default: `false`) 

However, the actual default value is null, which causes the following comparison to evaluate incorrectly:

const needsCustomAgent = Boolean(secure === false || certificateAuthorityFile);

When secure is null, the condition secure === false returns false, leading to unexpected behavior in the custom agent logic.

Solution

• Updated the default value of secure to false in both the GitLab configuration and schema
• This ensures consistency between the documented behavior and actual implementation

Additional Changes

• Updated documentation to clarify that GitLab tokens require api and self_rotate scopes