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

Composer.json: add link to security policy #338

Merged
merged 1 commit into from
Nov 24, 2023

Conversation

jrfnl
Copy link
Contributor

@jrfnl jrfnl commented Nov 24, 2023

Context

  • Improve discoverability of security policy

Summary

This PR can be summarized in the following changelog entry:

  • Improves discoverability of security policy in Packagist.

Relevant technical choices:

This is a new feature available since Composer 2.6.0, which was released a little while ago.

When this key is added, it will also show a link to the security policy on Packagist.

Refs:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • N/A

This is a new feature available since Composer 2.6.0, which was released a little while ago.

When this key is added, it will also show a link to the security policy on Packagist.

Refs:
* https://github.com/composer/composer/releases/tag/2.6.0
* composer/composer#11271
* composer/packagist#1353
@coveralls
Copy link

Pull Request Test Coverage Report for Build 6985524925

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 48.608%

Totals Coverage Status
Change from base Build 6925389201: 0.0%
Covered Lines: 1100
Relevant Lines: 2263

💛 - Coveralls

@jrfnl jrfnl merged commit f201e4b into trunk Nov 24, 2023
23 checks passed
@jrfnl jrfnl deleted the JRF/add-security-policy-file branch November 24, 2023 23:28
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