Add blog entry for v0.13.0 #114
Merged
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
qu1queee
added
the
kind/documentation
pull-request-size
bot
added
the
size/M
openshift-ci
bot
added
the
do-not-merge/work-in-progress
qu1queee
force-pushed
the
qu1queee/blog_v0.13.0
branch
from
eb999e5
to
7ca2950
Compare
pull-request-size
bot
added
size/L
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
Add installation steps
qu1queee
force-pushed
the
qu1queee/blog_v0.13.0
branch
from
7ca2950
to
89d3e28
Compare
rolfedh
approved these changes
Mar 28, 2024
|
|
||
| ### OCIArtifacts | ||
|
|
||
| When implementing prevention measures against path traversal during the extraction of an OCI artifact, we were too strict. We only needed to prevent /../ because this means to go one directory up. We still must allow `..` because a directory or file can contain two subsequent dots in its name. You can now use files and directories with two subsequent dots in its name when using an OCI artifact as source. |
There was a problem hiding this comment.
Suggested change
| When implementing prevention measures against path traversal during the extraction of an OCI artifact, we were too strict. We only needed to prevent /../ because this means to go one directory up. We still must allow `..` because a directory or file can contain two subsequent dots in its name. You can now use files and directories with two subsequent dots in its name when using an OCI artifact as source. | |
| When implementing prevention measures against path traversal during the extraction of an OCI artifact, we were too strict. We only needed to prevent `/../` because this means going up one directory. We still must allow `..` because a directory or file can contain two subsequent dots in its name. You can now use files and directories with two subsequent dots in its name when using an OCI artifact as source. |
Adarsh-jaiss
approved these changes
Mar 28, 2024
SaschaSchwarze0
approved these changes
Apr 2, 2024
openshift-ci
bot
added
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SaschaSchwarze0 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
qu1queee
force-pushed
the
qu1queee/blog_v0.13.0
branch
from
510fcc7
to
a2e2601
Compare
|
/hold cancel We have releases for the cli and build projects up! |
openshift-ci
bot
removed
the
do-not-merge/hold
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.
Changes
Add installation steps
Fixes #111
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes