INTEGRATION [PR#2493 > development/2.13] Bump vault with signatureAge of 0 fix - #2494
Closed
bert-e wants to merge 11 commits into
Closed
INTEGRATION [PR#2493 > development/2.13] Bump vault with signatureAge of 0 fix#2494bert-e wants to merge 11 commits into
bert-e wants to merge 11 commits into
Conversation
Pick up the vault fix accepting falsy constant params in request context validation: a signatureAge of 0 was dropped from the request context, failing policy evaluation (VAULT-735, found via RD-1890). Issue: ZENKO-5348
…t' into w/2.13/improvement/ZENKO-5348-bump-vault # Conflicts: # solution/deps.yaml
In order to handle race conditions, it makes an extra call to list versions after having created one. Issue: ZENKO-5224 (cherry picked from commit 7221694)
Older versions are broken in CI Issue: ZENKO-5224 (cherry picked from commit 9b723ea)
The 5 'Promote artifacts' tests fail on development/2.13 even though everything is pinned (action-gh-release@v2.5.0, act 0.2.75): the catthehacker act image (pulled with forcePull) now ships node 24 in its toolcache, which changed how unmatched mocked requests fail. action-gh-release@v2.5.0 never calls getReleaseByTag: it scans listReleases (findTagFromReleases) before creating the release. The second mocked listReleases reply contained the draft release, so the pre-creation scan found the target tag and took the update-existing path, issuing an updateRelease call no mock matches. This used to pass by accident: the unmatched request surfaced as a fast 404 which the action recovered from by creating the release; on node 24 it now hangs until an undici headers timeout and fails the step. Make the second listReleases reply draft-free so the action takes the create path, with every request matched by a mock. scality/action-artifacts@v4 (floating tag) is now a node24 action, which act 0.2.75 refuses to run: bump act to 0.2.84 as on development/2.14, and adapt the step-result parsing to the timing suffix newer act appends to step status lines. Issue: ZENKO-5317 (cherry picked from commit 5cbd598)
….13/improvement/ZENKO-5348-bump-vault
- there are conflicting -and unresolved- dependencies on @types/nodes in the project - bumping @types/node@^24.0.0 → 24.12.0 thus creates the duplicate definition - since we don't specify frozen-lock-file on yarn install, this bump happened unexpectedly Issue: ZENKO-5242
We have multiple un-pinned dependency on "@types/node", which used to resolve fine to 24.x release. We are now pulling 25.x, which has a different definition of `URLPattern`. Since we depend on this module multiple times, we have two incompatible types, which triggering TS2403. This happens because he lint-and-build-ctst job runs `yarn install` in CI without `--frozen-lockfile`. - When the commit were merged: @types/node@25.x had not been released yet (or was not the latest). So no problem. - Now @types/node@25.x is published and satisfies the various conditions. A fresh yarn install now resolves two separate versions into node_modules: 24.x and 25.x for >=13.7.0. Both declare URLPattern, causing TS2403. Issue: ZENKO-5242
….13/improvement/ZENKO-5348-bump-vault
The e2e deploy fails to pull gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0, which was removed when Google sunset the kubebuilder registry. zenko-operator v1.7.9 pulls the auth proxy from quay.io/brancz instead. Issue: ZENKO-5348
…t' into w/2.13/improvement/ZENKO-5348-bump-vault
benzekrimaha
force-pushed
the
w/2.13/improvement/ZENKO-5348-bump-vault
branch
from
August 17, 2026 11:49
92acb6b to
04872f0
Compare
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
4 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.
This pull request has been created automatically.
It is linked to its parent pull request #2493.
Do not edit this pull request directly.
If you need to amend/cancel the changeset on branch
w/2.13/improvement/ZENKO-5348-bump-vault, please follow thisprocedure:
git fetch git checkout w/2.13/improvement/ZENKO-5348-bump-vault # <amend or cancel the changeset by _adding_ new commits> git push origin w/2.13/improvement/ZENKO-5348-bump-vaultPlease always comment pull request #2493 instead of this one.