Repository navigation
fixing_relate_severities_v2_pipeline_failing - #2480
Open
saksham-rathore wants to merge 1 commit into
Open
saksham-rathore wants to merge 1 commit into
saksham-rathore wants to merge 1 commit into
Conversation
Signed-off-by: sammy <samrathore07062007@gmail.com>
saksham-rathore
force-pushed
the
fix/relate_severities_v2_pipeline_failing
branch
from
October 24, 2026 17:59
a2a11a7 to
9f2bec2
Compare
This branch has not been deployed
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.
Description
Fix issue #2479 by widening the primary key and sequence for:
vulnerabilities_advisoryv2_related_advisory_severities
This prevents PostgreSQL sequence exhaustion at 2147483647.
Changes
Testing