glab ci trace open old pipeline

Checklist

• I'm using the latest version of the extension (Run glab --version)
  • Extension version: 1.72.0
• Operating system and version: MacOS Sequoia 15.6.1 (24G90)
• Gitlab.com or self-managed instance? self-managed instance
• GitLab version (if self-managed) 18.3.2 (Use the version endpoint, like this: gitlab.my-company.com/api/v4/version)
• I have performed glab auth status to check for authentication issues
• Run the command in debug mode (like DEBUG=true glab mr list) and attach any useful output

Summary

When running glab ci trace, it open a 7 month old pipeline instead of the branch current one.

Environment

• OS: Darwin 24.6.0 arm64
• SHELL: /bin/zsh
• TERM: xterm-256color
• GLAB: glab 1.72.0 (294f0726)

Other:

Steps to reproduce

Push to a branch to start a pipeline and run glab ci trace

What is the current bug behavior?

It open a 7 month old pipeline.

What is the expected correct behavior?

It should open the current pipeline (the same opened by glab ci view that runs fine

Relevant logs and/or screenshots

$ DEBUG=true glab ci trace
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
[git config --get-all remote.origin.glab-resolved]
Getting jobs for pipeline 35617...

? Select pipeline job to trace:  [Use arrows to move, type to filter]
> sentry_upload_silcrow: [win10] (389150) - success
  sentry_tools (387264) - skipped
  sentry_release_joker (387263) - success
  sentry_release_silcrow (387262) - success
  macos_test_coverage_report_html (387261) - success
  macos_test_coverage_report_xml (387260) - success
  tools: [win10, MidiTool] (387259) - manual

Possible fixes

No idea