Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
automatic_updates
Manage
Activity
Members
Labels
Plan
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
project
automatic_updates
Merge requests
!115
Issue
#3248976
: Add API documentation for Package Manager
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Issue
#3248976
: Add API documentation for Package Manager
issue/automatic_updates-3248976:3248976-add-api-documentation
into
8.x-2.x
Overview
16
Commits
10
Pipelines
0
Changes
1
Merged
Adam G-H
requested to merge
issue/automatic_updates-3248976:3248976-add-api-documentation
into
8.x-2.x
3 years ago
Overview
15
Commits
10
Pipelines
0
Changes
1
Expand
0
0
Merge request reports
Viewing commit
a84d4fb2
Prev
Next
Show latest version
1 file
+
5
−
3
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
a84d4fb2
more ted feedback
· a84d4fb2
Adam G-H
authored
3 years ago
package_manager/package_manager.api.php
+
5
−
3
Options
@@ -129,9 +129,11 @@
* of the stage life cycle, to ensure that both the active directory and staging
* area are kept in a safe, consistent state:
*
* - No Composer operation which changes the lock file may be executed in the
* active directory while a staging area exists, either via Package Manager's
* API or externally.
* - If the composer.lock file is changed (e.g., by installing or updating a
* package) in the active directory after a staging area has been created,
* Package Manager will refuse to make any further changes to the staging
* area or apply the staged changes to the active directory.
* - The Drupal site must not have any pending database updates.
* - Composer must use HTTPS to download packages and metadata (i.e., Composer's
* secure-http configuration option must be enabled). This is the default
* behavior.
Loading