feat: disable settings upgrade & fix some bugs#431
Merged
Conversation
# Conflicts: # apps/settings/config/user/helm-charts/settings/templates/settings_deploy.yaml
# Conflicts: # apps/files/config/user/helm-charts/files/templates/files_deploy.yaml # apps/profile/config/user/helm-charts/profile/templates/profile_deployment.yaml
feat: update settings version to v0.1.71
# Conflicts: # apps/settings/config/user/helm-charts/settings/templates/settings_deploy.yaml
# Conflicts: # apps/settings/config/user/helm-charts/settings/templates/settings_deploy.yaml feat: update settings new version
eball
approved these changes
Sep 9, 2024
4 tasks
eball
pushed a commit
that referenced
this pull request
Apr 30, 2026
#2992) Bumps the following to address dependabot alerts in the kubesphere fork (both the root module and the staging kubesphere.io/api submodule): Indirect: - go.opentelemetry.io/otel v1.39.0 -> v1.41.0 (PATH hijack; baggage DoS) - go.opentelemetry.io/otel/sdk v1.39.0 -> v1.41.0 - github.com/moby/spdystream v0.5.0 -> v0.5.1 - go.mongodb.org/mongo-driver v1.3.2 -> v1.17.0 - github.com/prometheus/alertmanager v0.21.0 -> v0.28.1 Direct: - github.com/docker/docker v17.12.0-ce-rc1 (2020) -> v28.5.2 (auth bypass; off-by-one) - gopkg.in/square/go-jose.v2 v2.2.2 -> v2.6.0 - github.com/go-viper/mapstructure/v2 v2.2.1 -> v2.5.0 - migrate from github.com/dgrijalva/jwt-go (deprecated) to github.com/golang-jwt/jwt/v4 v4.5.2 - (staging api) golang.org/x/net -> v0.33.0 Code changes: - pkg/apiserver/authentication/authenticators/lldap/jwt.go: import path swap (jwt v4 is API-compatible with the dgrijalva v3 surface used here) - pkg/utils/term/term.go: github.com/docker/docker/pkg/term -> github.com/moby/term (the term package was extracted out of docker/docker in v20+; moby/term has identical GetFdInfo/GetWinsize signatures) Closes dependabot alerts #574, #551, #521, #432, #431, #347, #171, #170, #169, #168, #135, #134, #133, #132, #131, #130, #129, #128, #127, #126, #125, #124, #123, #122, #121, #117, #115. Pre-existing build errors in tools/lib (CRD generation) and the very old k8s.io/kubectl v0.21.2 (gnostic openapi mismatch) are unrelated to this PR; they exist on main and are not blocked or unblocked by these bumps. Made-with: Cursor
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
2 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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: