Bump glab CLI version to 1.111.0

What does this MR do and why?

Bumps the glab CLI pinned by Gitlab::DuoWorkflow::GlabSetup from 1.105.0 to 1.111.0 (released 2026-07-30). The pin drives the download URL used to install glab into Duo Agent Platform workloads; it has not moved since 2026-06-26 and was six releases behind.

The most relevant upstream change is fix(auth): include configured subfolder in OAuth URL, which complements the relative URL root support added to GlabSetup in !244235 (merged).

Two further auth fixes in 1.111.0 touch fields GlabSetup#config_file_command writes into config.yml:

  • preserving oauth2_refresh_token during reauthentication
  • sending a non-blank username with plain token logins

On the keyring change

1.111.0 also makes the OS keyring the default credential store. This does not affect us: the choice is made per-host during glab auth login, and persisted as use_keyring. GlabSetup writes ~/.config/glab-cli/config.yml directly and never invokes auth login, so the absent use_keyring key keeps file-based storage in effect.

How to set up and validate locally

ee/spec/lib/gitlab/duo_workflow/glab_setup_spec.rb asserts against described_class::VERSION rather than a literal, so it covers the new value without changes:

bundle exec rspec ee/spec/lib/gitlab/duo_workflow/glab_setup_spec.rb

14 examples, 0 failures.

Follow-up

This pin is bumped by hand each time. A Renovate config to automate it is proposed in https://gitlab.com/gitlab-org/frontend/renovate-gitlab-bot.

Merge request reports

Loading
Loading