Update security policy for 1.x and 2.x #14081
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With the 1.x release we're extending security support for Qiskit to 1 yr. We still only support 1.x for general bugfixes for 6 months after the 2.0.0 release. But for 1.x if any security vulnerabilities are identified we will provide fixes for that up to 1 yr after the release of 2.0.0. This was reflected in the 1.4.0 release notes and is on the version strategy docs: https://docs.quantum.ibm.com/open-source/qiskit-sdk-version-strategy but we forgot to update the security policy document in the Qiskit repo. This commit fixes this oversight.
|
One or more of the following people are relevant to this code:
|
ElePT
reviewed
Mar 24, 2025
Co-authored-by: Elena Peña Tapia <57907331+ElePT@users.noreply.github.com>
Pull Request Test Coverage Report for Build 14041444933Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
ElePT
approved these changes
Mar 25, 2025
mergify bot
pushed a commit
that referenced
this pull request
Mar 25, 2025
* Update security policy for 1.x and 2.x With the 1.x release we're extending security support for Qiskit to 1 yr. We still only support 1.x for general bugfixes for 6 months after the 2.0.0 release. But for 1.x if any security vulnerabilities are identified we will provide fixes for that up to 1 yr after the release of 2.0.0. This was reflected in the 1.4.0 release notes and is on the version strategy docs: https://docs.quantum.ibm.com/open-source/qiskit-sdk-version-strategy but we forgot to update the security policy document in the Qiskit repo. This commit fixes this oversight. * Update SECURITY.md Co-authored-by: Elena Peña Tapia <57907331+ElePT@users.noreply.github.com> --------- Co-authored-by: Elena Peña Tapia <57907331+ElePT@users.noreply.github.com> (cherry picked from commit cd05386)
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 25, 2025
* Update security policy for 1.x and 2.x With the 1.x release we're extending security support for Qiskit to 1 yr. We still only support 1.x for general bugfixes for 6 months after the 2.0.0 release. But for 1.x if any security vulnerabilities are identified we will provide fixes for that up to 1 yr after the release of 2.0.0. This was reflected in the 1.4.0 release notes and is on the version strategy docs: https://docs.quantum.ibm.com/open-source/qiskit-sdk-version-strategy but we forgot to update the security policy document in the Qiskit repo. This commit fixes this oversight. * Update SECURITY.md Co-authored-by: Elena Peña Tapia <57907331+ElePT@users.noreply.github.com> --------- Co-authored-by: Elena Peña Tapia <57907331+ElePT@users.noreply.github.com> (cherry picked from commit cd05386) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
With the 1.x release we're extending security support for Qiskit to 1 yr. We still only support 1.x for general bugfixes for 6 months after the 2.0.0 release. But for 1.x if any security vulnerabilities are identified we will provide fixes for that up to 1 yr after the release of 2.0.0. This was reflected in the 1.4.0 release notes and is on the version strategy docs:
https://docs.quantum.ibm.com/open-source/qiskit-sdk-version-strategy
but we forgot to update the security policy document in the Qiskit repo. This commit fixes this oversight.
Details and comments