You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: changelogs/October_3rd_2025.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,15 +25,11 @@ Latest version: **v0.6.127**
25
25
26
26
This is a PR that was opened as a normal PR following a previous draft PR opened which touches the same project:
27
27
28
-

29
-
30
28
Expected behaviour is that the pr should plan normally no issues. Current behaviour (digger pro) is that it fails to plan because locked by another pr
31
29
32
30
This behaviour is for existing PRs that would be opened as drafts and have a dnaling lock present. In current develop branch the "digger unlock" comment on the other PR would be ignored so it would not unlock and the other PR would be stuck and not able to aquire the lock. In this PR we now force unlock even when it is a draft PR configured to be ignored so the digger unlock will allow the user to plan on the other PR that was blocked by the draft PR
33
31
34
32
35
-

36
-
37
33
4. Smoother `taco login` with Microsoft/Entra, and copy-pasteable paths to run OpenTaco Statesman on AWS with HTTPS out of the box: More here: [#2284](https://github.com/diggerhq/digger/pull/2284)
38
34
5. GCP (Cloud Run) quickstart guide for deploying Statesman with Artifact Registry + Cloud Run: [#2275](https://github.com/diggerhq/digger/pull/2275)
0 commit comments