-
Notifications
You must be signed in to change notification settings - Fork 66
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
Update module github.com/evanphx/json-patch to v5.9.11+incompatible (release/v0.4) - autoclosed #601
Closed
renovate-rancher
wants to merge
44
commits into
release/v0.4
from
renovate/github.com-evanphx-json-patch-5.x
Closed
Update module github.com/evanphx/json-patch to v5.9.11+incompatible (release/v0.4) - autoclosed #601
renovate-rancher
wants to merge
44
commits into
release/v0.4
from
renovate/github.com-evanphx-json-patch-5.x
Conversation
This file contains 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
[v0.4] Bump copyright year
Proper validation of GlobalRole `rules`, plus fix (TomL) to make validation not namespaced.
…ith the new version (#345) * Fix all errors from golangci-lint * Remove deprecated skip-dirs and skip-files from golangci.json * Remove useless exclude-files
[v0.4] update rke to v1.5.9-rc2
[v0.4] update rancher/pkg/apis to latest commit
* [v0.4.6] s4: Fixes 374 (#392) * Update rancher/rancher/pkg/apis dependency * Verify ExternalRules in RoleTemplates If the feature flag external-rules is enabled, the validation for RT follows this sequence: - 1) Reject if externalRules are provided and the user doesn’t have escalate permissions on RoleTemplates. - 2) Validate the policy rules defined in externalRules the same way as the already existing rules field. This validation leverages Kubernetes’ upstream validation. Webhook will validate this only if external is set to true. - 3) Use externalRules for resolving rules if provided. - 4) Use backing ClusterRole in the local cluster if externalRules are not provided. - 5) Reject if externalRules are not provided and there is no backing ClusterRole in the local cluster. For PRTB or CRTB: - 1) Use externalRules for resolving rules if provided. - 2) Use backing ClusterRole in the local cluster if externalRules are not provided. The previous verification process applies if the external-rules feature flag is disabled. * Allow Restricted Admin to update external-rules feature flag (#102) --------- Co-authored-by: Raul Cabello Martin <[email protected]> Co-authored-by: Jonathan Crowther <[email protected]> * bump rancher to commit 2145c8e9d6034579caa6279856c59679f1102cf3 --------- Co-authored-by: Peter Matseykanets <[email protected]>
[v0.4] [GHA] Migrate v0.4 CI to GHA
* Add a check for the agent-tls-mode setting (#416) * Keep importing a wrangler v2 package
[v0.4] update rke to v1.5.11-rc4
…ng RoleTemplates (#398) return false instead
Don't error if external-rules feature flag is not found
Verify that the actual value of the annotation is string "true" when checking that it's ok to change the tls-mode from `system-store` to `strict`. Co-authored-by: Eric Promislow <[email protected]>
Some indirect dependencies are still rc'd, but I think it's out of scope to try to solve that here, as the policy change to avoid rc dependencies in releases was made quite recently.
[v0.4] Bump both rke and dymamiclistener to their release versions
bump rke and rancher/rancher/pkg/apis
[v0.4] update rke to v1.5.13-rc.2
* Prevents dropping unknown cluster fields Signed-off-by: Dharmit Shah <[email protected]> * add test for v3 cluster mutator & add rke to replace in go.mod adding rke to replace section will avoid pulling in rc versions when updating pkg/apis in webhook
* Add sync deps workflow * Add sync deps workflow * List changes in PR description * Add usage and error handling for pkg/apis version extraction * Update format of changes for PR description * Fix missing new line in sync script * Make default rancher branch release/v2.8
Co-authored-by: Webhook Sync Bot <[email protected]>
* Fix PR not triggering CI * Fix token permission * Fix quote
Co-authored-by: rancher-pr-and-push-webhook[bot] <181785884+rancher-pr-and-push-webhook[bot]@users.noreply.github.com>
Co-authored-by: rancher-pr-and-push-webhook[bot] <181785884+rancher-pr-and-push-webhook[bot]@users.noreply.github.com>
00c82b7
to
8fb0358
Compare
8fb0358
to
ff71cdd
Compare
ff71cdd
to
adf2bce
Compare
adf2bce
to
7b7a40a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v5.6.0+incompatible
->v5.9.11+incompatible
Release Notes
evanphx/json-patch (github.com/evanphx/json-patch)
v5.9.11+incompatible
Compare Source
v5.9.10+incompatible
Compare Source
v5.9.0+incompatible
Compare Source
v5.8.1+incompatible
Compare Source
v5.8.0+incompatible
Compare Source
v5.7.0+incompatible
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.