-
Notifications
You must be signed in to change notification settings - Fork 85
chore(release): release 1.1.3 #8889
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
Conversation
Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
doc: lock config documentation Signed-off-by: pujavs <pujas.works@gmail.com>
Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🟢 Risk threshold not exceeded. Change Summary (click to expand)The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective. Summary: The changes in this pull request cover a range of updates to the Janssen project, including version updates for various Helm charts and container images. The overall focus of these changes seems to be on promoting development versions to stable, production-ready releases. From an application security perspective, the changes do not appear to introduce any obvious security vulnerabilities. However, it's important to review the actual code changes, release notes, and any related security advisories to ensure that the updates do not contain any security-related fixes or improvements that should be considered. Additionally, the application security team should review the overall security posture of the Janssen project, including the configuration of various components, the handling of sensitive information, and the security of the deployment process. Ensuring that the application is properly secured and follows security best practices is crucial, even for routine version updates. Files Changed:
Powered by DryRun Security |
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
…/jans#8889 Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
…/jans#8889 (#1766) Signed-off-by: moabu <47318409+moabu@users.noreply.github.com>
* chore: 1.1.3-SNAPSHOT to 1.1.3 Signed-off-by: moabu <47318409+moabu@users.noreply.github.com> * chore: modify image tags Signed-off-by: moabu <47318409+moabu@users.noreply.github.com> * chore: add 1.1.3 to version list in readme Signed-off-by: moabu <47318409+moabu@users.noreply.github.com> * docs: lock configuration schema declaration (#8862) doc: lock config documentation Signed-off-by: pujavs <pujas.works@gmail.com> * chore: update Dockerfile Signed-off-by: moabu <47318409+moabu@users.noreply.github.com> * chore: update prereelase chart flag Signed-off-by: 6D40 moabu <47318409+moabu@users.noreply.github.com> --------- Signed-off-by: moabu <47318409+moabu@users.noreply.github.com> Signed-off-by: pujavs <pujas.works@gmail.com> Co-authored-by: pujavs <43700552+pujavs@users.noreply.github.com> Former-commit-id: 86e9c31
This PR is to prepare for the release of 1.1.3
Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with
docs:
to indicate documentation changes or if the below checklist is not selected.