arminc / k8s-platform-lcm

A faster and easier way to manage the lifecycle of applications and tools, running and living around your Kubernetes platform
MIT License
185 stars 14 forks source link

Bump helm.sh/helm/v3 from 3.3.4 to 3.6.2 #154

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps helm.sh/helm/v3 from 3.3.4 to 3.6.2.

Release notes

Sourced from helm.sh/helm/v3's releases.

Helm 3.6.2

Helm v3.6.2 is a regression fix release from v3.6.1. The security fix released in v3.6.1 caused a bug to surface that was previously only an issue in uncommon situations. v3.6.2 provides a solution to this bug.

The community keeps growing, and we'd love to see you there!

  • Join the discussion in Kubernetes Slack:
    • for questions and just to hang out
    • for discussing PRs, code, and bugs
  • Hang out at the Public Developer Call: Thursday, 9:30 Pacific via Zoom
  • Test, debug, and contribute charts: ArtifactHub/packages

Installation and Upgrading

Download Helm v3.6.2. The common platform binaries are here:

This release was signed with 672C 657B E06B 4B30 969C 4A57 4614 49C2 5E36 B98E and can be found at @​mattfarina keybase account. Please use the attached signatures for verifying this release using gpg.

The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with bash.

What's Next

  • 3.6.3 will contain only bug fixes and is planned for release on July 14, 2021
  • 3.7.0 is the next feature release and will be released on September 8, 2021.

Changelog

  • Fix the url being set by WithURL on the getters ee407bdf364942bcb8e8c665f82e15aa28009b71 (Matt Farina)
  • Adding test for user/pass without repo on Helm install aff309d983d59db0450d656f56eb109c21ac6c7d (Matt Farina)

Helm 3.6.1

Helm v3.6.1 is a security (patch) release. Users are strongly recommended to update to this release.

While working on the Helm source, a Helm core maintainer discovered a situation where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. More information can be found in the security advisory.

Note: if updating to v3.6.1 causes issues downloading charts from password protected repositories it may mean the charts are being served from a different domain than the repository. If you trust the other domain to receive the credentials and want to pass the credentials to that domain name you can use the new --pass-credentials flag. This flag works with helm repo add as well as commands that accept the --repo flag.

The community keeps growing, and we'd love to see you there!

... (truncated)

Commits
  • ee407bd Fix the url being set by WithURL on the getters
  • aff309d Adding test for user/pass without repo on Helm install
  • 61d8e8c tweak basic handling
  • 7f2df64 bump version to v3.6.0
  • 37d3dac Merge pull request #9492 from morlay/master
  • 2462575 Merge branch 'main' into master
  • d4cc130 Merge pull request #9621 from sagikazarmark/ingress-v1
  • 8f49890 Merge pull request #9040 from thatsmydoing/helm3-kube-version
  • 3f283c7 Merge pull request #9425 from joelanford/pkg-ready
  • 51097a5 Merge pull request #9595 from sbose78/1.21
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 3 years ago

Superseded by #157.