Update docker/login-action action to v3.3.0 (release/v0.3) - autoclosed #453
Conversation
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
![renovate-rancher[bot]](https://avatars.githubusercontent.com/in/269045?s=60&v=4){kind=small}
…than its presence
…nt-update-on-prtb [0.3] Disallow changes to ServiceAccount field on PRTB update rather than its presence
[v0.3] Bump copyright year and remove s390x runner
[0.3] Upgrade to k8s 1.27
Bump go 1.20
[v0.3] update rke to v1.4.18-rc1
* [v0.3.10] s4: Fixes 374 (#393) * Update rancher/rancher/pkg/apis dependency * [v0.3.s4] Backport Verify ExternalRules in RoleTemplates (#103) 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. * [v0.3.s4] Allow Restricted Admin to update external-rules feature flag (#104) --------- Co-authored-by: Jonathan Crowther <[email protected]> Co-authored-by: Raul Cabello Martin <[email protected]> * bump rancher to commit 56a742be417f937c9189068110270271906556ba --------- Co-authored-by: Peter Matseykanets <[email protected]>
renovate-rancher
bot
added
the
dependencies
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
9ecff0f to
344cddc
Compare
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
344cddc to
51c04cb
Compare
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
51c04cb to
52b18a0
Compare
Signed-off-by: Guilherme Macedo <[email protected]>
…valuating RoleTemplates (#529) Co-authored-by: Raul Cabello Martin <[email protected]>
* Migrate v0.3 to GHA - backport changes to v0.5 - use k8s 1.27 - include setting capi.port -- this stopped happening with v 0.4 - rancher 2.7 chart still insists on k8s 1.26 tops - Install rancher against an up-to-date chart. * Revert to the original version of golangci-lint * Back out other unrelated changes. * Don't change the Helm version.
* Update webhook rancher mods to be in sync with rancher/rancher's * Pull in more updated dependencies.
renovate-rancher
bot
changed the title
renovate-rancher
bot
changed the title
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
52b18a0 to
50d4a30
Compare
renovate-rancher
bot
changed the title
renovate-rancher
bot
changed the base branch from
release/v0.6
to
release/v0.5
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
50d4a30 to
a6256a3
Compare
renovate-rancher
bot
changed the title
renovate-rancher
bot
changed the base branch from
release/v0.5
to
release/v0.4
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
a6256a3 to
67b0907
Compare
renovate-rancher
bot
changed the title
renovate-rancher
bot
changed the base branch from
release/v0.4
to
release/v0.3
renovate-rancher
bot
force-pushed
the
renovate/docker-login-action-3.x
branch
from
67b0907 to
a0f404b
Compare
renovate-rancher
bot
changed the title
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:
v3.2.0->v3.3.0Release Notes
docker/login-action (docker/login-action)
v3.3.0Compare Source
Full Changelog: docker/login-action@v3.2.0...v3.3.0
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.