Skip to content
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

Added dashboard and test manifests for 1.3.19 #4951

Merged
merged 1 commit into from
Aug 19, 2024

Conversation

bshien
Copy link
Contributor

@bshien bshien commented Aug 19, 2024

Description

Manually added the manifests for dashboard and testing for the 1.3.19 release.

Issues Resolved

Part of #4888

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

components:
- name: OpenSearch-Dashboards
repository: https://github.com/opensearch-project/OpenSearch-Dashboards.git
ref: tags/1.3.19
Copy link
Collaborator

@prudhvigodithi prudhvigodithi Aug 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be '1.3' for all the components. We update to tags once the release is completed.

@gaiksaya gaiksaya added the manifest-ci-check Run manifest ci check label Aug 19, 2024
Signed-off-by: Brandon Shien <bshien@amazon.com>
@gaiksaya
Copy link
Member

gaiksaya commented Aug 19, 2024

@peterzhuamazon @prudhvigodithi Do you know why the manifest check skips on second commit/push?
Have seen this behavior in past too

@gaiksaya gaiksaya added manifest-ci-check Run manifest ci check and removed manifest-ci-check Run manifest ci check labels Aug 19, 2024
@gaiksaya gaiksaya merged commit 71f69a5 into opensearch-project:main Aug 19, 2024
16 checks passed
@zelinh
Copy link
Member

zelinh commented Aug 19, 2024

@peterzhuamazon @prudhvigodithi Do you know why the manifest check skips on second commit/push? Have seen this behavior in past too

I think because of the force push. I think our workflow won't consider force event as the trigger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

4 participants