Skip to content
GitLab
Explore
Sign in
Open
11
Merged
29
Closed
1
All
41
Merge trains
Recent searches
Loading
{{ formattedKey }}
{{ title }}
{{ help }}
{{name}}
@{{username}}
None
Any
{{name}}
@{{username}}
None
Any
{{name}}
@{{username}}
None
Any
{{name}}
@{{username}}
None
Any
{{name}}
@{{username}}
{{name}}
@{{username}}
None
Any
Upcoming
Started
{{title}}
None
Any
{{title}}
None
Any
{{title}}
None
Any
{{name}}
Yes
No
Yes
No
{{title}}
{{title}}
{{title}}
Updated date
Issue #3331332: The update:lightning command should echo the final "composer require" command if composer.json is not writable
!24
· created
Jan 05, 2023
by
Adam G-H
6.0.x
Merged
updated
Jan 05, 2023
Issue #3331131: Make update:lightning command add components' dependencies directly into the top-level composer.json
!23
· created
Jan 04, 2023
by
Adam G-H
Merged
updated
Jan 05, 2023
Issue #3331552: The update command should not say existing constraints were unchanged
!25
· created
Jan 06, 2023
by
Adam G-H
6.0.x
Merged
updated
Jan 06, 2023
Issue #3331567: Improve reporting of update:lightning command
!26
· created
Jan 06, 2023
by
Adam G-H
6.0.x
Merged
updated
Jan 06, 2023
Issue #3331599: The update command should always update to the next major version of the components
!27
· created
Jan 06, 2023
by
Adam G-H
Merged
updated
Jan 06, 2023
Issue #3331618: Remove the update:lightning command entirely
!28
· created
Jan 06, 2023
by
Adam G-H
6.0.x
Merged
updated
Jan 06, 2023
Issue #3331621: Update command does not properly scan for database updates
!29
· created
Jan 06, 2023
by
Adam G-H
Merged
updated
Jan 06, 2023
Issue #3331634: Put the upgrade functionality of the update:lightning command behind a --upgrade flag
!30
· created
Jan 06, 2023
by
Adam G-H
Merged
updated
Jan 06, 2023
Issue #3331663: If the update:lightning command can't find composer.json, the exception should mention the --composer-file option
!31
· created
Jan 07, 2023
by
Adam G-H
Merged
updated
Jan 07, 2023
Prev
1
2
Next