Repository navigation
fix: bump cpex-secrets-detection to 0.2.0 - #4338
Merged
Merged
Conversation
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com>
brian-hussey
force-pushed
the
fix/cpex-secrets-detection-020
branch
from
April 20, 2026 13:13
6203dae to
472f328
Compare
gcgoncalves
pushed a commit
that referenced
this pull request
Apr 23, 2026
* fix: bump cpex-secrets-detection to 0.2.0 Signed-off-by: lucarlig <luca.carlig@ibm.com> * Update .secrets.baseline Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com> --------- Signed-off-by: lucarlig <luca.carlig@ibm.com> Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com> Co-authored-by: Brian Hussey <brian.hussey@ie.ibm.com>
brian-hussey
added a commit
that referenced
this pull request
May 5, 2026
* fix: bump cpex-secrets-detection to 0.2.0 Signed-off-by: lucarlig <luca.carlig@ibm.com> * Update .secrets.baseline Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com> --------- Signed-off-by: lucarlig <luca.carlig@ibm.com> Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com> Co-authored-by: Brian Hussey <brian.hussey@ie.ibm.com> Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com>
msureshkumar88
pushed a commit
that referenced
this pull request
May 13, 2026
* fix: bump cpex-secrets-detection to 0.2.0 Signed-off-by: lucarlig <luca.carlig@ibm.com> * Update .secrets.baseline Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com> --------- Signed-off-by: lucarlig <luca.carlig@ibm.com> Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com> Co-authored-by: Brian Hussey <brian.hussey@ie.ibm.com>
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
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.
What changed
cpex-secrets-detection>=0.2.0in the[plugins]extra.tool.uv.exclude-newer-packagecutoff to April 20, 2026 souvcan resolve the new release once it is published.Why
0.1.0forcpex-secrets-detection.0.2.0.Blocker
cpex-secrets-detection 0.1.0as the latest release as of April 20, 2026.uv lock --upgrade-package cpex-secrets-detectioncurrently fails for that reason, souv.lockis intentionally unchanged in this draft PR.Validation
git commit.uv lock --upgrade-package cpex-secrets-detectionfails because only0.1.0is currently available on PyPI.