chore(security): drop stale safety ignore 88512 + dependabot watchdog for Flink manifest - #222
Merged
Merged
Conversation
…ependabot watchdog - safety: PyUp corrected the 88512 cross-ecosystem false positive (verified 2026-07-20: 0 findings on the pinned langchain stack), so the ignore is removed and any resurfacing fails the job loudly. - The remaining pyarrow ignore (SFTY-20260217-93940) is requalified from "latent bump task" to "blocked upstream": apache-flink 2.3.0 is the newest PyPI release and its beam chain cannot reach pyarrow 23.0.1. - dependabot: the Flink runtime manifest (src/processing/flink_jobs) was in no pip ecosystem entry, so the apache-flink release that unblocks the ignore would go unnoticed. Add a weekly pip entry as the watchdog. - .gitignore: /grok_task_*.md joins the root-level session-notes guard. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DORA Metrics
|
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
2 participants
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
--ignore 88512from the safety step: PyUp corrected the cross-ecosystem false positive (langchain). Verified 2026-07-20 with safety 2.3.5 on the pinned stack (langchain==1.3.13,langchain-core==1.4.9,langchain-text-splitters==1.1.2,langsmith==0.10.2): 0 findings. If the entry ever resurfaces, the job fails loudly instead of masking it.apache-beam<=2.61(pyarrow<17) and itself capspyarrow<21— the CVE fix (pyarrow 23.0.1) is unreachable in that bucket until the next apache-flink release. Blocked upstream, not by our pin.src/processing/flink_jobs— the Flink runtime manifest was in no pip ecosystem entry, so the apache-flink release that unblocks the ignore would go unnoticed. Weekly, individual PRs,chore(deps,flink)prefix. (A version-bump PR there will intentionally fail the image'sFLINK_VERSIONassert until taken through a deliberate bump session — that's the alarm, not a defect.).gitignore:/grok_task_*.mdjoins the root-level session-notes guard.Verification
yaml.safe_loadon both changed YAML files; pip directories now['/', '/src/processing/flink_jobs', '/sdk', '/integrations'].tests/unit/test_security_workflow.py+tests/unit/test_ci_sdk_ts_gate.py: 5 passed.git status: only the three intended tracked files modified; grok task spec no longer untracked.🤖 Generated with Claude Code