Skip to content

sync: Main sync develop #6583

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 21 commits into from
May 19, 2025
Merged

sync: Main sync develop #6583

merged 21 commits into from
May 19, 2025

Conversation

vikramdevtron
Copy link
Contributor

Description

Fixes #

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


satyampsoni and others added 20 commits January 6, 2025 16:19
misc: Sync reference charts to main
fix: Remove funtionName from labels from pg_query_duration_seconds_* metrics
* Updated release-notes files

* Update beta-releasenotes.md

* Updated release notes

* Updated release notes

* Updated release notes

* Updated release notes

* Updated release notes

* misc: exposed the postgres endpoint in migrator and app-sync (#6570)

* exposed the postgres endpoint

* renamed the parameter

---------

Co-authored-by: Badal Kumar Prusty <badalkumar@Badals-MacBook-Pro.local>

* Switched Kubelink to Headless mode & added retention for minio-cache-bucket

* Updated minio added statement for no retention policy

* Updated release notes

* updated minio condition

* Updated notifier to 99e2f3cd-372-32893 tag in values file

* Updated kubewatch to da156379-419-32900 tag in values file

* Updated kubelink to da156379-564-32903 tag in values file

* Updated git-sensor to da156379-200-32905 tag in values file

* Updated dashboard to c5dfd7aa-690-32907 tag in values file

* Updated release notes

* Updated lens to da156379-333-32910 tag in values file

* Updated ci-runner to da156379-138-32911 tag in values file

* Updated image-scanner to da156379-141-32912 tag in values file

* Updated chart-sync to da156379-836-32914 tag in values file

* Updated hyperion to fe2a86b-280-32916 tag in values file

* Updated devtron to fe2a86b-434-32917 tag in values file

* Updated the version in scripts

* sorted the devtron-images.txt.source

* Update devtron-bom.yaml

* Update kubelink.yaml

* Update devtron.yaml

* Updated devtron to ccae002-434-32949 tag in values file

* Updated hyperion to ccae002-280-32950 tag in values file

* Updated devtron to 667bd63-434-32952 tag in values file

* Updated hyperion to 667bd63-280-32953 tag in values file

* Update releasenotes.md

* Update release-notes-v1.6.0.md

* Update release-notes-v1.6.0.md

* Update releasenotes.md

* Update release-notes-v1.6.0.md

* Update releasenotes.md

* Update release-notes-v1.6.0.md

* Update releasenotes.md

* Update releasenotes.md

* Update release-notes-v1.6.0.md

* Update Chart.yaml

* Update devtron-bom.yaml

---------

Co-authored-by: akshatsinha007 <156403098+akshatsinha007@users.noreply.github.com>
Co-authored-by: Badal Kumar <130441461+badal773@users.noreply.github.com>
Co-authored-by: Badal Kumar Prusty <badalkumar@Badals-MacBook-Pro.local>
Co-authored-by: akshatsinha007 <akshat.sinha@devtron.ai>
Co-authored-by: Pawan Mehta <117346502+pawan-mehta-dt@users.noreply.github.com>
Copy link

gitguardian bot commented May 19, 2025

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
9257608 Triggered Base64 AWS keys 667bd63 scripts/devtron-reference-helm-charts/deployment-chart_4-21-0/test-values.json View secret
2763127 Triggered Generic High Entropy Secret fc4aa57 scripts/devtron-reference-helm-charts/deployment-chart_4-21-0/secrets-test-values.yaml View secret
141558 Triggered Generic High Entropy Secret a92dcd5 scripts/devtron-reference-helm-charts/deployment-chart_4-21-0/env-values.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. 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


🦉 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.

Copy link

The migration files have successfully passed the criteria!!

Copy link

The migration files have successfully passed the criteria!!

Copy link

@vikramdevtron vikramdevtron merged commit bcb1103 into develop May 19, 2025
7 checks passed
@vikramdevtron vikramdevtron deleted the main-sync-develop-19may branch May 19, 2025 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.