Skip to content

Support encrypted values for definitions.https.url - #16632

Merged
michaelklishin merged 1 commit into
mainfrom
mk-tagged-values-for-definitions.https.url
Jun 8, 2026
Merged

michaelklishin merged 1 commit into
mainfrom
mk-tagged-values-for-definitions.https.url

Conversation

@michaelklishin

Copy link
Copy Markdown
Collaborator

Note that this key is a tricky one: it includes
colon-prefixed values that are NOT encrypted
since that's the typical URI, URL format.

This is a continuation to #16541, including one
backwards-compatible internal data type change
from a tagged string to a tagged binary, for
consistency with the rest of the comparable keys
across the entire codebase.

Note that this key is a tricky one: it includes
colon-prefixed values that are NOT encrypted
since that's the typical URI, URL format.

This is a continuation to #16541, including one
backwards-compatible internal data type change
from a tagged string to a tagged binary, for
consistency with the rest of the comparable keys
across the entire codebase.
@michaelklishin michaelklishin added this to the 4.4.0 milestone Jun 8, 2026
@michaelklishin
michaelklishin merged commit ea761b5 into main Jun 8, 2026
188 checks passed
@michaelklishin
michaelklishin deleted the mk-tagged-values-for-definitions.https.url branch June 8, 2026 21:50
michaelklishin added a commit that referenced this pull request Jun 8, 2026
Support encrypted values for `definitions.https.url` (backport #16632)
michaelklishin added a commit that referenced this pull request Jun 9, 2026
Support encrypted values for `definitions.https.url` (backport #16632) (backport #16634)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant