This repository was archived by the owner on May 25, 2026. It is now read-only.
fix(client): tailor 403 guidance to PAT vs CI job token (DOT-432) - #104
Merged
ichoosetoaccept merged 3 commits intoMay 15, 2026
Conversation
added 3 commits
May 15, 2026 12:56
Bundled housekeeping pass: - Bump all 5 outdated packages to latest (all minor/patch): - dotenv 17.4.1 -> 17.4.2 - zod 4.3.6 -> 4.4.3 - @biomejs/biome 2.4.10 -> 2.4.15 - @types/bun 1.3.11 -> 1.3.14 - @types/node 25.5.2 -> 25.8.0 - Bump biome.json $schema URL to match the new Biome version (was pinned to 2.3.10, lagging the actual installed version). - Ignore .claude/worktrees/ and .serena/ in .gitignore so agent-harness state stops leaking into git status — and, more importantly, stops breaking 'bun run check' (Biome's config discovery was treating the worktree biome.json copies as nested root configurations and bailing). Verified: bun run check, bun run build, bun test all green (292 pass).
Member
Author
|
This change is part of the following stack: Change managed by git-spice. |
ApprovabilityVerdict: Approved This PR improves 403 error messages by providing guidance tailored to the authentication method (PAT vs CI job token). The change only affects error message text, includes tests, and carries no risk to runtime behavior beyond better diagnostics. You can customize Macroscope's approvability policy. Learn more. |
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
macroscopeapp
Bot
dismissed
their stale review
May 15, 2026 11:41
Dismissing prior approval to re-evaluate a6675e7
ichoosetoaccept
deleted the
ismart/dot-432-improve-403-error-guidance-for-ci_job_token-users
branch
May 15, 2026 11:43
github-actions Bot
pushed a commit
that referenced
this pull request
May 15, 2026
## [2.28.2](v2.28.1...v2.28.2) (2026-05-15) ### Bug Fixes * **client:** tailor 403 guidance to PAT vs CI job token (DOT-432) ([#104](#104)) ([868bab2](868bab2))
|
🎉 This PR is included in version 2.28.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tailor 403 error guidance to PAT vs CI job token in
GitLabClientPreviously, all 403 errors showed generic PAT scope guidance, which was not actionable for CI job token users. Now,
throwIfForbiddenin gitlab-client.ts calls a newscopeGuidance(tokenHeader)function that returns token-type-specific messages: PAT users see guidance about Access Token scopes, while CI job token users are directed to their project's CI/CD token access settings.🖇️ Linked Issues
Resolves DOT-432, which identified that CI job token users received misleading PAT-specific guidance on 403 errors.
Macroscope summarized a6675e7.