issue: #90
Made it possible to select multiple lines of diff when creating MR discussions.
The API is difficult to use, so there is a possibility that AI will not be able to create appropriate payloads.
🚀 Breaking Changes:
- Updated version from 1.0.63 to 1.0.64
- Added cookie-based authentication details in README
📝 Details:
- Enhanced Docker instructions in README
- Updated package-lock.json and package.json with new version
* feat: add cookie-based authentication support for GitLab instances 🍪
- Add GITLAB_AUTH_COOKIE_PATH environment variable support
- Handle #HttpOnly_ prefix in cookie files properly
- Enable redirect following when cookies are present
- Maintain compatibility with existing token-based auth
* chore: prepare fork for npm publishing as @mattweg/gitlab-mcp
- Update package name to @mattweg/gitlab-mcp
- Bump version to 1.0.63-fork.1
- Add attribution to original author zereight
- Add deprecation notice referencing upstream PR #100
- Add repository and homepage URLs for fork
* fix: remove duplicate documentation line
- removed the duplicate GITLAB_AUTH_COOKIE_PATH from README.md
* fix: move cookie header outside conditional block for universal auth support
- Move cookie header setting outside if/else block to ensure it applies
to both old (Private-Token) and new (Bearer) GitLab authentication
- Fixes issue where cookies were only set for Bearer token auth
- Maintains backward compatibility with existing authentication methods
- Enables cookie-based authentication for all GitLab instance types
Resolves authentication failures when using GITLAB_AUTH_COOKIE_PATH
with GitLab instances that require cookie-based authentication.
* 1.0.63
* fix: add support for macOS cookie format in auth cookie parsing 🍪
- Add fallback parsing for macOS cookie format
- Handle cookie files with different structure than standard Netscape format
- Maintain compatibility with existing Linux cookie parsing
- Extract cookie name and value from space-separated format
Resolves authentication failures when using GITLAB_AUTH_COOKIE_PATH on macOS systems.
* 1.0.64
* chore: update version to 1.0.63-fork.3
* fix: implement proper cookie jar authentication for macOS
- Replace static cookie string with fetch-cookie + tough-cookie
- Add proper Netscape cookie format parsing with domain context
- Enable automatic cookie handling during OAuth2 redirects
- Fixes authentication issues on macOS with enterprise SSO
* chore: update version to 1.0.63-fork.4
* feat: add cookie-based authentication support for enterprise GitLab instances
Add support for Netscape cookie file authentication to enable access to
enterprise GitLab instances that use SSO/OAuth2 redirects.
- Add GITLAB_AUTH_COOKIE_PATH environment variable
- Implement cookie jar with proper domain handling for redirects
- Use conditional fetch assignment: cookie-enabled when path configured
- Maintains backward compatibility: no cookies = original behavior
- Zero changes to existing fetch() calls throughout codebase
Enables authentication flows like: curl -L -b ~/.midway/cookie
Useful for enterprise environments with federated authentication.
* chore: update to fork version 1.0.63-fork.5 with cookie auth support
* feat: add cookie-based authentication support for enterprise GitLab instances
Add support for Netscape cookie file authentication to enable access to
enterprise GitLab instances that use SSO/OAuth2 redirects.
- Add GITLAB_AUTH_COOKIE_PATH environment variable
- Implement cookie jar with proper domain handling for redirects
- Use conditional fetch assignment: cookie-enabled when path configured
- Maintains backward compatibility: no cookies = original behavior
- Zero changes to existing fetch() calls throughout codebase
Enables authentication flows like: curl -L -b ~/.midway/cookie
Useful for enterprise environments with federated authentication.
* feat: implement robust cookie-based authentication with hybrid parsing
- Add support for Netscape cookie file format with #HttpOnly_ prefix handling
- Implement hybrid approach using tough-cookie's parse() for robust cookie parsing
- Add automatic session establishment for enterprise GitLab authentication
- Support cookie file path via GITLAB_AUTH_COOKIE_PATH environment variable
- Integrate with fetch-cookie for automatic redirect handling and session persistence
- Ensure compatibility with Midway enterprise authentication flow
This enables seamless authentication with enterprise GitLab instances that require
cookie-based authentication while maintaining clean, maintainable code using
widely-supported packages (tough-cookie + fetch-cookie).
* chore: bump version to 1.0.63-fork.6 with ultra-clean cookie auth
* fix: correct package name to @mattweg/gitlab-mcp for proper npx dependency resolution
- Fix package name mismatch that prevented npx from installing dependencies
- Bump version to 1.0.63-fork.7
- This resolves cookie authentication issues by ensuring fetch-cookie and tough-cookie are properly installed
* Improve cookie authentication with robust session establishment
* feat: add cookie-based authentication support
This feature adds support for cookie-based authentication with GitLab instances by:
- Adding a new GITLAB_AUTH_COOKIE_PATH environment variable to specify the path to a Netscape-format cookie file
- Implementing a cookie jar parser that handles standard Netscape cookie format
- Adding session establishment logic that checks for GitLab session cookies
- Ensuring all API requests use the authenticated session
This allows the MCP server to authenticate with GitLab instances that use cookie-based authentication, which is particularly useful for instances that require SSO or other authentication methods that don't support personal access tokens.
---------
Co-authored-by: Moon (mattweg's AI assistant) <moon+ai-assistant@mattweg.dev>
Co-authored-by: Matt Weg <mattweg@amazon.com>
GitLab API returns null for notification_level when users are group owners,
instead of a numeric value. This change updates the Zod schema to accept
both number and null values for notification_level in both project_access
and group_access permission objects.
Fixes TypeError when parsing repository permissions for group owners.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
- Add optional `limit` and `offset` parameters to get_pipeline_job_output
- Default limit is 1000 lines when pagination is used
- Returns lines from the end of the log, with configurable offset
- Includes truncation metadata showing what was skipped
- Maintains backward compatibility (no parameters = full log)
This prevents large CI logs from overwhelming AI tooling context windows
while still providing access to the most recent and relevant log output.
🚀 Breaking Changes:
- Removed incorrect `Bearer ` prefix from Private-Token header in legacy authentication mode
- Fixed authentication issues for older GitLab instances with private tokens
📝 Details:
- Ensures proper API authentication for both new and legacy GitLab configurations
🚀 Breaking Changes:
- Updated merge request functionality with new options
- Improved handling of assignee usernames in issue listings
📝 Details:
- Added support for `remove_source_branch` and `squash` options for merge requests
- Fixed issue with assignee username handling in issue listing
- Generated RELEASE_NOTES.md from CHANGELOG.md
Image files in GitLab MR discussions use x/y coordinates instead of line numbers. This fix allows proper handling of image diff comments.
Co-authored-by: Peter Xu <px.peter.xu@gmail.com>
