Repository navigation
chore: update firewall image to 2.10.0 - #62
Open
socket-release-bot[bot] wants to merge 1 commit into
Open
socket-release-bot[bot] wants to merge 1 commit into
socket-release-bot[bot] wants to merge 1 commit into
Conversation
This branch has not been deployed
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
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.
Updates deployment defaults to the published Socket Firewall image
2.10.0and bumps the Helm chart patch version.Image:
socketdev/socket-registry-firewall:2.10.0Release run
Manual review is required before merging:
Note
Low Risk
Version and documentation-only bumps to deployment defaults; runtime behavior depends on the 2.10.0 image release, which should be reviewed separately.
Overview
Bumps the default Socket Registry Firewall container image from
2.9.10to2.10.0and aligns the Helm chart patch release to0.11.10(appVersionandimage.tagstay in sync).The same pins are applied to EKS CloudFormation defaults (
ChartVersion,FirewallImageTag), the DNS-override example values file, and related README tables—no template or values behavior changes beyond the version strings.Reviewed by Cursor Bugbot for commit 4c5741c. Configure here.