Merged
Conversation
feat: update semantic.yml
feat: multiple repo support for release notes
Reorganized conditions to ensure server version filtering occurs before slicing the response by size and offset. This enhances code readability and preserves logical consistency in response processing.
Improved handling of pagination by introducing checks for the presence of offset and size query parameters. Adjusted logic to conditionally apply pagination based on provided parameters and defaults. This enhances clarity and ensures more robust request handling.
Replaced custom version parsing logic with the Masterminds/semver library for improved accuracy and maintainability. Added the dependency to `go.mod` and updated related files accordingly. This change ensures better handling of semantic versioning edge cases.
This commit includes the Masterminds/semver library in the vendor directory, complete with its source code, CI configurations, documentation, and license. This addition ensures version parsing and constraint checking features are available as part of the project.
fix: stack Manager issues
feat: "currency rate conversion for finops"
misc: Doc rag
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 24822213 | Triggered | Generic Password | 7d59fe6 | devtron-docs-rag-server/docker-compose.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
|
prakash100198
previously approved these changes
Feb 17, 2026
SATYAsasini
dismissed
prakash100198’s stale review
The base branch was changed.
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
prakash100198
approved these changes
Feb 17, 2026
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
5 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.
Fixes https://github.com/devtron-labs/sprint-tasks/issues/2802