-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Comparing changes
Open a pull request
base repository: helm/helm
base: v3.13.0
head repository: helm/helm
compare: v3.13.1
- 11 commits
- 14 files changed
- 8 contributors
Commits on Oct 12, 2023
-
chore(deps): bump golang.org/x/text from 0.11.0 to 0.13.0
Bumps [golang.org/x/text](https://github.com/golang/text) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/golang/text/releases) - [Commits](golang/text@v0.11.0...v0.13.0) --- updated-dependencies: - dependency-name: golang.org/x/text dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit 58ccfc0)
Configuration menu - View commit details
-
Copy full SHA for ff8e61d - Browse repository at this point
Copy the full SHA ff8e61dView commit details -
Increased release information key name max length.
Helm release names are limited to 53 characters. By default, Release information is stored in Kubernetes as secrets, and the secret's name structure follows the pattern "sh.helm.release.v1.<release name up to 53 characters>.v<release revision>." However, in the case of using an SQL backend, this release information key is stored in the release_v1 table, and the table constraint currently limits the key name length to 67 characters. This limitation may not be suitable for release names that are within Helm's 53-character limit and need to accommodate the additional "sh.helm.release.v1." prefix and the release revision suffix. Signed-off-by: abrarcv170 <78675575+abrarcv170@users.noreply.github.com> (cherry picked from commit 4199be8)
Configuration menu - View commit details
-
Copy full SHA for 52a029d - Browse repository at this point
Copy the full SHA 52a029dView commit details -
chore(deps): bump oras.land/oras-go from 1.2.3 to 1.2.4
Bumps [oras.land/oras-go](https://github.com/oras-project/oras-go) from 1.2.3 to 1.2.4. - [Release notes](https://github.com/oras-project/oras-go/releases) - [Commits](oras-project/oras-go@v1.2.3...v1.2.4) --- updated-dependencies: - dependency-name: oras.land/oras-go dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit 102e931)
Configuration menu - View commit details
-
Copy full SHA for c99a8ac - Browse repository at this point
Copy the full SHA c99a8acView commit details -
Write latest version to get.helm.sh bucket
The purpose of this change is leverage this output for the get-helm script. It will provide the following benefits: - Use true semver so a future release of a patch version so a future release of a patch version does not cause an unexpected minor/major version downgrade - Avoid reliance on the github api which has rate limiting. This will also increase availability by reducing the number of systems the get-helm script depends on. - Simplify the script so parsing json is not necessary - Increase uptime by only requiring the Azure CDN to be available Signed-off-by: Ian Zink <zforce@gmail.com> (cherry picked from commit 0619d08)
Configuration menu - View commit details
-
Copy full SHA for 6101393 - Browse repository at this point
Copy the full SHA 6101393View commit details -
Fix missing run statement on release action
Signed-off-by: Ian Zink <zforce@gmail.com> (cherry picked from commit 21ea847)
Configuration menu - View commit details
-
Copy full SHA for 0901269 - Browse repository at this point
Copy the full SHA 0901269View commit details -
fix(registry): address anonymous pull issue
The assumption that either a username and/or password OR an error is returned appears to be wrong, and results in an error later on which looks something like the following: ``` failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3AXXX%2FYYY%3Apull&service=registry.docker.io: 401 Unauthorized ``` To mitigate this, confirm we actually have one of the values before setting the `Authorization` header. Co-authored-by: Joe Julian <me@joejulian.name> Signed-off-by: Hidde Beydals <hidde@hhh.computer> (cherry picked from commit fe4c01f)
Configuration menu - View commit details
-
Copy full SHA for 0ac7894 - Browse repository at this point
Copy the full SHA 0ac7894View commit details -
remove useless print during prepareUpgrade
Signed-off-by: b4nks <b4nks@protonmail.com> (cherry picked from commit f004d42)
Configuration menu - View commit details
-
Copy full SHA for 0e7ec78 - Browse repository at this point
Copy the full SHA 0e7ec78View commit details -
fix(registry): unswallow error
Signed-off-by: Hidde Beydals <hidde@hhh.computer> (cherry picked from commit da3c666)
Configuration menu - View commit details
-
Copy full SHA for 06e4fb1 - Browse repository at this point
Copy the full SHA 06e4fb1View commit details -
Configuration menu - View commit details
-
Copy full SHA for bae7b32 - Browse repository at this point
Copy the full SHA bae7b32View commit details -
Add missing with clause to release gh action
Signed-off-by: Ian Zink <zforce@gmail.com> (cherry picked from commit 9d3d17a)
Configuration menu - View commit details
-
Copy full SHA for 6f9ad87 - Browse repository at this point
Copy the full SHA 6f9ad87View commit details -
Fixing precedence issue with the import of values.
The ordering should be: 1. User specified values (e.g CLI) 2. Parent chart values 3. Imported values 4. Sub-chart values This enables parnet charts to import large set of values from a child and then override select values. This change is needed for backwards compatibility. Fixes #12460 Signed-off-by: Matt Farina <matt.farina@suse.com> (cherry picked from commit 25371e2)
Configuration menu - View commit details
-
Copy full SHA for 3547a4b - Browse repository at this point
Copy the full SHA 3547a4bView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.13.0...v3.13.1