GitHub
10/23/2025, 7:33 AMGitHub
10/24/2025, 1:07 AMsetup-codeql action has been added which is similar to init, except it only installs the CodeQL CLI and does not initialize a database. Do not use this in production as it is part of an internal experiment and subject to change at any time. #3204
See the full CHANGELOG.md for more information.
---
### Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻️ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
---
• If you want to rebase/retry this PR, check this box
---
This PR was generated by Mend Renovate. View the repository job log.
runatlantis/atlantisGitHub
10/25/2025, 1:42 AMGitHub
10/26/2025, 1:34 AMGitHub
10/27/2025, 1:09 AMnpx playwright init-agents with your client of choice to generate the latest agent definitions:
### Generate agent files for each agentic loop
### Visual Studio Code
npx playwright init-agents --loop=vscode
### Claude Code
npx playwright init-agents --loop=claude
### opencode
npx playwright init-agents --loop=opencode
[!NOTE]
VS Code v1.105 (currently on the VS Code Insiders channel) is needed for the agentic experience in VS Code. It will become stable shortly, we are a bit ahead of times with this functionality!Learn more about Playwright Agents #### New APIs • New methods page.consoleMessages() and page.pageErrors() for retrieving the most recent console messages from the page • New method page.requests() for retrieving the most recent network requests from the page • Added `--test-list` and `--test-list-invert` to allow manual specification of specific tests from a file #### UI Mode and HTML Reporter • Added option to
'html' reporter to disable the "Copy prompt" button
• Added option to 'html' reporter and UI Mode to merge files, collapsing test and describe blocks into a single unified list
• Added option to UI Mode mirroring the --update-snapshots options
• Added option to UI Mode to run only a single worker at a time
#### Breaking Changes
• Event browserContext.on('backgroundpage') has been deprecated and will not be emitted. Method browserContext.backgroundPages() will return an empty list
#### Miscellaneous
• Aria snapshots render and compare input placeholder
• Added environment variable PLAYWRIGHT_TEST to Playwright worker processes to allow discriminating on testing status
#### Browser Versions
• Chromium 141.0.7390.37
• Mozilla Firefox 142.0.1
• WebKit 26.0
---
### Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻️ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
---
• If you want to rebase/retry this PR, check this box
---
This PR was generated by Mend Renovate. View the repository job log.
runatlantis/atlantisGitHub
10/28/2025, 3:44 AMGitHub
10/29/2025, 9:41 AMGitHub
10/29/2025, 6:49 PMSupports a basepath if you're hosting Atlantis under a path.However, setting a URL with a basepath only updates the URLs in the Atlantis UI; none of the Atlantis endpoints are updated to include the basepath. This PR updates the mux Router so that if the
--atlantis-url includes a base path, all the endpoints will also be prefixed with the same base path.
## why
My team is hoping to host multiple Atlantis instances behind a single AWS ALB, using path-based routing.
ALBs don't let us modify the request path, so we need Atlantis to be able to serve from a base path.
This PR allows us to do that.
Right now, this will append this functionality to the --atlantis-url flag. I could understand if you would prefer a separate flag, like --atlantis-base-path, to make this functionality more explicit. If you would prefer that, please let me know and I can update the PR.
## tests
• I've added some tests to verify that the base path is correctly extracted from the --atlantis-url flag
I have deployed this with and without a basepath set to manually verify the behaviour. I would love to add more tests to verify that the endpoints are correctly registered with the base path, but I'm not sure of a good way to do that. If you have any guidance on how I could do that, please let me know.
## references
The base path support was originally added in #213
runatlantis/atlantisGitHub
10/30/2025, 2:51 AMGitHub
10/30/2025, 5:59 PMapply_requirements, this gives extra context to the shell command being executed
## tests
## references
#5779
runatlantis/atlantisGitHub
10/31/2025, 12:54 AMGitHub
10/31/2025, 3:19 AMGitHub
10/31/2025, 4:29 PMGitHub
10/31/2025, 5:33 PMgh-allow-mergeable-bypass-apply and the PR is blocked, atlantis will always report that the PR is unmergeable and unapproved.
## why
Atlantis should ignore these global workrun because they are not related and cannot be related to required workflows since they don't have a file related to it.
## tests
I have used my data structure that I received from the same graphql query atlantis does and added it as a test case.
## references
closes #5925
runatlantis/atlantisGitHub
11/01/2025, 1:41 AMGitHub
11/01/2025, 11:18 PMmerge_method: squash configuration option.
## tests
• Added comprehensive test coverage for GitLab squash merge functionality
• Existing GitHub merge method tests continue to pass
• All GitLab VCS client tests pass
• Automerge integration tests pass
• Tested locally with both squash and regular merge methods
## references
• Addresses #5415 - Allow merge method as configurable option in atlantis.yaml
• Follows established patterns from GitHub VCS client implementation
• GitLab API documentation: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request
runatlantis/atlantisGitHub
11/02/2025, 11:57 AMGitHub
11/03/2025, 1:16 AMGitHub
11/04/2025, 2:32 AMGitHub
11/04/2025, 4:27 AMApprovePolicies but we returning as if it ran the PolicyCheck command.
As far as I can tell this bug has been present since this code was introduced: af2a806#diff-eb466bb07e603dbf2a2a91c776b4d812bf330b3dc02fcaf762380b0078296937R174
I frankly don't quite understand what this does, but if you look at the rest of the doXYZ in plan_command_runner, they follow a particular pattern of referring to commands, and this one simply seems to have been typod.
## tests
N/A
## references
N/A
runatlantis/atlantisGitHub
11/04/2025, 5:11 AMGitHub
11/05/2025, 2:11 AMGitHub
11/05/2025, 2:14 AMGitHub
11/06/2025, 2:11 AMJobURL to the PlanSuccess model.
This PR also renames the LockURLGenerator to URLGenerator as it will be used for generating more than just the lock url. Currently the code already uses the router to fulfill this interface, so I have added the function GenerateProjectJobURL which it gets from the router.
## Why
In certain cases, it's necessary to hide Terraform plan output in GitHub comments—such as in public repositories where the output may contain sensitive information. However, users may still need access to the plan details via a secure URL, such as one behind a firewall or ingress.
By including the job URL in the GitHub comment template (in addition to the existing GitHub check link), we provide users with clear guidance on why the output is hidden and where they can access it instead.
## Tests
Tested locally by overriding the comment template and verifying the job URL was correctly included.
## References
• Atlantis Issue #5391
## Notes
• I encountered issues running pegomock unless I downgraded Go to 1.23.0 in go.mod.
• Currently, the job URL is added only to *plan success*—I considered adding it to PolicyCheckResults, but I’m unsure whether those results are accessible via a URL. Would appreciate any feedback on this!
runatlantis/atlantisGitHub
11/06/2025, 2:14 AMGitHub
11/07/2025, 2:03 AMGitHub
11/07/2025, 2:05 PM./atlantis server --bitbucket-user '<user>' --bitbucket-api-user '<user@example.com>' --bitbucket-token '<token>' --repo-allowlist '*' --log-level info
{"level":"info","ts":"2025-11-07T10:54:04.448-0300","caller":"server/server.go:343","msg":"Supported VCS Hosts: BitbucketCloud","json":{}} {"level":"info","ts":"2025-11-07T10:54:04.814-0300","caller":"server/server.go:504","msg":"Utilizing BoltDB","json":{}} {"level":"info","ts":"2025-11-07T10:54:04.827-0300","caller":"policy/conftest_client.go:168","msg":"failed to get default conftest version. Will attempt request scoped lazy loads DEFAULT_CONFTEST_VERSION not set","json":{}} {"level":"info","ts":"2025-11-07T10:54:04.827-0300","caller":"server/server.go:1114","msg":"Atlantis started - listening on port 4141","json":{}} {"level":"info","ts":"2025-11-07T10:54:04.827-0300","caller":"scheduled/executor_service.go:51","msg":"Scheduled Executor Service started","json":{}}
Without the flag:
./atlantis server --bitbucket-user '<user>' --bitbucket-token '<token>' --repo-allowlist '*' --log-level info
{"level":"info","ts":"2025-11-07T10:54:19.114-0300","caller":"server/server.go:343","msg":"Supported VCS Hosts: BitbucketCloud","json":{}} {"level":"info","ts":"2025-11-07T10:54:19.341-0300","caller":"server/server.go:504","msg":"Utilizing BoltDB","json":{}} {"level":"info","ts":"2025-11-07T10:54:19.350-0300","caller":"policy/conftest_client.go:168","msg":"failed to get default conftest version. Will attempt request scoped lazy loads DEFAULT_CONFTEST_VERSION not set","json":{}} {"level":"info","ts":"2025-11-07T10:54:19.352-0300","caller":"server/server.go:1114","msg":"Atlantis started - listening on port 4141","json":{}} {"level":"info","ts":"2025-11-07T10:54:19.352-0300","caller":"scheduled/executor_service.go:51","msg":"Scheduled Executor Service started","json":{}}
## references
• closes #5696
runatlantis/atlantisGitHub
11/08/2025, 1:47 AMGitHub
11/09/2025, 1:39 AMGitHub
11/10/2025, 1:13 AM