-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update file-secure to 0.2.27 #18500
update file-secure to 0.2.27 #18500
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test connector=connectors/source-file-secure
Build FailedTest summary info:
|
i'm actually not sure if |
/publish connector=connectors/source-file-secure
if you have connectors that successfully published but failed definition generation, follow step 4 here |
@@ -9,5 +9,5 @@ RUN pip install . | |||
ENV AIRBYTE_ENTRYPOINT "python /airbyte/integration_code/main.py" | |||
ENTRYPOINT ["python", "/airbyte/integration_code/main.py"] | |||
|
|||
LABEL io.airbyte.version=0.2.26 | |||
LABEL io.airbyte.version=0.2.27 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also be incrementing FROM airbyte/source-file:0.2.26
to 0.2.27
to correspond to the source-file
bump. However, for some reason I haven't been able to figure out immediately, using that version causes a SAT test to fail. The priority is to fix the build pipeline and not introduce a potential security regression so we should use the prior version instead of commenting out the acceptance test.
/publish connector=connectors/source-file-secure
if you have connectors that successfully published but failed definition generation, follow step 4 here |
c840c77
to
9f691de
Compare
/test connector=connectors/source-file-secure
Build PassedTest summary info:
|
/publish connector=connectors/source-file-secure
if you have connectors that successfully published but failed definition generation, follow step 4 here |
source-file
was bumped to 0.2.27 in #18481 but we forgot to also bumpsource-file-secure
which will break cloud publish since the connector image will be missing. This fixed that