Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable27] fix(deps): Allow composer plugin explicitly #1776

Merged
merged 1 commit into from
Jan 8, 2024

Conversation

nickvergessen
Copy link
Member

Fixes:


In PluginManager.php line 743:
                                                                                                                                                                            
  bamarni/composer-bin-plugin contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe.                 
  You can run "composer config --no-plugins allow-plugins.bamarni/composer-bin-plugin [true|false]" to enable it (true) or disable it explicitly and suppress this excepti  
  on (false)                                                                                                                                                                
  See https://getcomposer.org/allow-plugins                                                                                                                                 
                                                                                                                                                                            

audit [--no-dev] [-f|--format FORMAT] [--locked]

@nickvergessen
Copy link
Member Author

/backport to stable26

Copy link
Collaborator

@Antreesy Antreesy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nickvergessen nickvergessen merged commit 5e8a725 into stable27 Jan 8, 2024
25 checks passed
@nickvergessen nickvergessen deleted the bugfix/noid/allow-composer-plugin branch January 8, 2024 09:49
@backportbot-nextcloud
Copy link

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin stable26

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

Error: Unknown error

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants